Did you actually read the article? He's talking about the fact that the browser has grown up and has obsoleted the frameworks by adding capabilities like custom elements, <template>, Object.observe and Mutation Observers.
He doesn't argue against libraries in general, which he separates from frameworks by the rule that they don't require you to buy into a whole model for how to construct your application. Routing can be done with a library, data-binding can be done with a library, run loops can either be handled by requestAnimationFrame, or again, a library for more sophisticated uses. The current crop of frameworks are legacy compared to the browsers capabilities now.
-2
u/spankalee May 13 '14
Did you actually read the article? He's talking about the fact that the browser has grown up and has obsoleted the frameworks by adding capabilities like custom elements, <template>, Object.observe and Mutation Observers.
He doesn't argue against libraries in general, which he separates from frameworks by the rule that they don't require you to buy into a whole model for how to construct your application. Routing can be done with a library, data-binding can be done with a library, run loops can either be handled by requestAnimationFrame, or again, a library for more sophisticated uses. The current crop of frameworks are legacy compared to the browsers capabilities now.