You're viewing a comment by Darwin and its responses.

March 15, 2016, 22:14

i think in my previous comment, i did not said he should build the core out of spring (or any framework). What im trying to point out is, before you head building your own core, study the internals of other framework, and you are right, cherry pick the features that you need.
that is to contradict the author's statement about
"Frameworks are hard to learn and this knowledge is generally useless"
which is not true, you can learn a lot from a framework, and if he have hard time learning a framework, how do he expect me to believe he can build one from the scratch?

i mean, sure, you can build your own bike by cutting down your own rubber tree for the tires and mining your own iron directly from the mountains to build its components. But how do you expect me to believe you can do a decent one, if you are having hard time operating a simple bike-spare-parts assembling machine?

master any framework first, before rolling your own.
dont go for "core", just for the mere reason that you are finding hard to understand frameworks.

Comment Responses

ares Permalink
November 24, 2017, 09:46

"finding hard to understand frameworks."
understand what boilerplate? you ppl are brainwashed

Reply To This Comment

(why do I need your e-mail?)

(Your twitter handle, if you have one.)

Type the word "cdrom_508": (just to make sure you're a human)

Please preview the comment before submitting to make sure it's OK.