Also, I’m writing emails to ask for interviews for Debuggers, my blog about interesting bugs.
ps: I’m sure you guys have lots of cool debugging stories to tell. Send me a message if you’re interested in an interview.
I think the author may be missing the point of frameworks.
They’re not only about solving technical problems, they’re also about setting a baseline. The framework draws a line in the sand: “this is how we do AJAX”, “this is how we render JSON data”.
For most teams it’s a win because you don’t have to create ad-hoc conventions.
Agreed on the need create conventions, and the fact that frameworks help create a baseline for the whole team, but do we need so much code (like in Ember or Angular) to achieve this goal?
Well, I think the problem is nobody ever chose a framework because of its nice conventions. Features sell frameworks.
Because of this framework writers get sidetracked into thinking they’ve got to add more features, making in turn their frameworks less generic.
Framework providers also have an implicit contract in that they are responsible for the universe. Doesn’t supply a database driver that plays with the framework ORM and transaction system, it is now the framework author’s responsibility.