You're replying to a comment by Carlos Gortaris.

March 14, 2016, 19:01

Firstly, I'm impressed the amount of trolls around here (no reading comprehension and just cursing everyone). Very odd.

Secondly, about the article's contents, I agree on most of the arguments but I'll add that sometimes there are business needs that fit perfectly well (or up to a good percentage) with frameworks and the team's skills set. I wouldn't say it happens a lot since in my experience, it doesn't, but when it does, it's a good choice that would provide much advantage on time and effort.

Thirdly, to those readers/commentators that see in this article a root cause given by a bad experience with frameworks, well... it could be true but that's a long shot. What's being explicitly put here is an example of a successful project that's being made with zero frameworks... I mean, that's the motivation, right there! Why would you think otherwise?

Finally, I'd like to stress the importance of choosing a framework or not given the business needs and the team you might want to put into the task. To me, a good framework would embrace typical business needs and add value to the solution by getting work done by the team in less time and with a high confidence level of correctness underlying on it (those are the things to evaluate). It's up to the developers decision to choose the framework's features instead of the core language to solve things that, like Peter said, were programmed like 20 years ago and they work just fine even now.

Reply To This Comment

(why do I need your e-mail?)

(Your twitter handle, if you have one.)

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

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