11–12 of 12 posts
No I don't.
I'm not at all a fan of stuffing application logic into the HTML; it means that I need to look both in the JavaScript and in the HTML. I'm also not a fan of generating the structure of a page in JavaScript, but I find this slightly more forgiveable since I know the JS can always manipulate the page.
Then again, I also refuse to view Angular as JavaScript - I find skimming over Angular code incomprehensible.
For web apps, jQuery is "dead" in the same sense that string-concatenated HTTP responses are dead.
They certainly exist and are used, but there is a level of abstraction (templates) that supercede -- or should supercede -- that functionality for most developers most of the time.
If I'm writing a "hello world" web server, I probably won't be using templates. But if I'm writing a web server serving HTML that I want to be maintainable at any non-trivial complexity, I'll be using a framework/library.
Sure, you can use jQuery, and yes Angular uses it (or jqlite) for cross-browser DOM interaction, but that will not be the predominant or most visible tool in any moderately complex web app.
Front end development is coming around to the advantages of MVC, and the current generation of tools reflect that.
jQuery is not dead; it is simply no longer the highest level of abstraction for creating web apps.