jQuery is still my bread and butter for DOM manipulation and events. I've found it to be much more readable than vanilla JS.
Can you elaborate on what JQuery does for you that you can't do with modern JS features such as fetch and query selectors?
I loved jQuery, and still do (2019)
11–20 of 189 posts
Re: I loved jQuery, and still do (2019)
#12Re: I loved jQuery, and still do (2019)
#13Earlier quoted context omitted.
That's 30KB over the network and 90KB of JS code in memory so that you don't need to learn about 5 standardized browser API methods that are the same in every browser going back to IE9 then. No doubt that gives you a better developer experience but I don't think your users are thanking you.
The internets users managed to live with this terrible 30k burden in the late 2000's when it was the only choice. I think probably in 2021 when 30kb is a rounding error on page sizes they can also probably manage it.
This feels like a false equivalence; how many of those 2000s users were browsing the web on mobile compared to today?
Re: I loved jQuery, and still do (2019)
#14I am deploying Vue ui's now without webpack or any kind of bundler – jQuery and I have been through hell and back but I do wouldn't say I love it.
Re: I loved jQuery, and still do (2019)
#15JQuery is a tour de force of API design. Still use it in all my web projects.
Re: I loved jQuery, and still do (2019)
#16jQuery is still my bread and butter for DOM manipulation and events. I've found it to be much more readable than vanilla JS.
That's 30KB over the network and 90KB of JS code in memory so that you don't need to learn about 5 standardized browser API methods that are the same in every browser going back to IE9 then. No doubt that gives you a better developer experience but I don't think your users are thanking you.
I'm not happy about it, but the reality is that 120kB is small potatoes in the modern web world. Would it be better without, sure? But there are bigger fish to fry. If jQuery helps the developer achieve their design and development goals, that will play out better for the end-user. It's not ideal, but it's realistic.
Re: I loved jQuery, and still do (2019)
#17Earlier quoted context omitted.
That's 30KB over the network and 90KB of JS code in memory so that you don't need to learn about 5 standardized browser API methods that are the same in every browser going back to IE9 then. No doubt that gives you a better developer experience but I don't think your users are thanking you.
I don’t follow. Is the implication here that users can identify an experience difference cause by a 30KB over-the-wire asset, or more, a 90KB in memory one? I know I certainly wouldn’t claim to have that ability myself even on low quality networks.
If you're a user on a spotty mobile connection in a rural location on a low-end device ... both.
Re: I loved jQuery, and still do (2019)
#18I love jQuery.
I can just drop in the library onto any existing webpage, and have almost complete control of the DOM with just a few lines of code. And the built in actions and animations are all so simple and perfect for the web. And the structure and naming is so good that I rarely need to look up any references anymore.
I get that browser support isn't as important as it used to be, but it is nice to know that you can just use an effect in jQuery and it will just work exactly as you expect it.
Re: I loved jQuery, and still do (2019)
#19Django templates + Bootstrap + jQuery is all I've ever needed to make great, modern websites. Server-side rendering with some nice layouts and interactivity on the frontend. I've tried some of the SPA frameworks and I've always felt like my productivity tanked.
Re: I loved jQuery, and still do (2019)
#20jQuery is still my bread and butter for DOM manipulation and events. I've found it to be much more readable than vanilla JS.
Can you elaborate on what JQuery does for you that you can't do with modern JS features such as fetch and query selectors?
This page gives a pretty good overview of why jQuery is still relevant: http://youmightnotneedjquery.com/
Requests have gotten better with "fetch", but unfortunately, the "modern" DOM API is quite bad in some parts, making lots of stuff unnecessarily verbose. On top of that, it's really odd that the DOM API is not compatible with for-of loops, which could have been a selling point.