But he write what most of the developers misunderstood. Many people use Angular for jobs, that will be easier and faster done with a simple jQuery.
"Get the job done" got replaced with "its cool to use xyz".
"Get the job done" got replaced with "its cool to use xyz".
Each time I've thought 'there has to be more to do than that'.
If I were doing JQueries - there would be an entire stack of event driven DOM updates still to code.
But it depends on the complexity and size of a project and how many developers are involved. I prefer frameworks too, but for a small WebApp, it is overkill to use frameworks like angular/backbone/whatever.
Of course this means that for simple jobs jQuery may be better suited, unless you're trying to LEARN Angular, in which case it makes sense to struggle through trivial apps with complex tools until it clicks. None of this supports the article's thesis, of course, which is something akin to "I dont understand this, it must be lame!"
Which is funny because it started out as a way for web desginers (not developers) to learn how to write apps.