JQuery is dead
ralphsaunders.co.uk
JQuery is dead
1–10 of 12 posts
Re: JQuery is dead
#2Re: JQuery is dead
#3jQuery is not dead, and until DOM apis converge across browser vendors and become 100x easier to use it will remain active.
Re: JQuery is dead
#4So you replace 4 lines of jQuery with 40 lines of barely readable Angular (for somebody who hasn't worked with it), and declare jQuery dead?
> Yeah, jQuery is dead not because frameworks make you write better code - we know they don’t - but because your framework does DOM manipulation better than you ever could.
If what I need to accomplish can be done in 4 lines of jQuery, I use jQuery. When I know there's going to be a ton of DOM manipulation, I reach for a suitable framework/library because I know the mess I'll end up in if I try scaling up the 4 lines of jQuery to handle a complex web application.
Re: JQuery is dead
#5You realize Angular depends on jQuery right? And that extending Angular with new functionality involves using jQuery... jQuery is not dead, and until DOM apis converge across browser vendors and become 100x easier to use it will remain active.
Re: JQuery is dead
#6Re: JQuery is dead
#7Re: JQuery is dead
#8You realize Angular depends on jQuery right? And that extending Angular with new functionality involves using jQuery... jQuery is not dead, and until DOM apis converge across browser vendors and become 100x easier to use it will remain active.
I'm pretty sure you can use Angular without jQuery and even without using the jQuery-lite thing they have in it. I've moved on from Angular now but I definitely didn't rely on jQuery at all during my end of my Angular days.
For all intents and purposes, jqLite should be considered equivalent to jQuery for my argument.
Re: JQuery is dead
#9Re: JQuery is dead
#10Although SPAs, frontend frameworks and the model of communicating microservices is gaining lots of traction and visibility for web applications (particularly paid services that replace former desktop apps), plain old server-side CRUD that renders template variables from a data model is still going to be the dominant paradigm on the web at large, not to mention more of a conceptual neat fit to begin with.
In some ways I predict there will be a sort of resurgence in server-side CRUD frameworks again as being the hot trend you read about on HN, once people found out that you can easily build real-time, reactive UIs without having to context switch and directly deal with the often subpar client-side interfaces. Furthermore, the act of generating HTML and JavaScript from native language constructs will be lauded as a great time-saver, not to mention giving the same benefits of the so-called "isomorphism" that platforms like Node are hailed for. For examples of these concepts, see the Nitrogen and N2O frameworks (both Erlang).