Pretty much this. Angular isn't there to replace jQuery or do simple things that can be done in minutes in jQuery; Angular's for building applications. I like the analogy in the first comment on the page itself.
The article links to another page where the author rants about why Angular sucks; the second paragraph already indicates the author is trying to do direct DOM manipulation, which is exactly what Angular tries to prevent you from doing. It's an abstraction layer (amongst other things).
tl;dr I wonder if the author ever worked on a production-sized single page application.
Comments
Pretty much this. Angular isn't there to replace jQuery or do simple things that can be done in minutes in jQuery; Angular's for building applications. I like the analogy in the first comment on the page itself.
The article links to another page where the author rants about why Angular sucks; the second paragraph already indicates the author is trying to do direct DOM manipulation, which is exactly what Angular tries to prevent you from doing. It's an abstraction layer (amongst other things).
tl;dr I wonder if the author ever worked on a production-sized single page application.