jQuery 4.1.0
- hax0ron3 - 9764 sekunder sedanAlthough jQuery isn't very relevant these days, I still find its pattern of chaining a sequence of methods on a set chosen by a selector to be a beautiful example of going with a language's features.
- CM30 - 7913 sekunder sedanI'm a tad surprised jQuery still exists, though it's kinda neat it does. Always interesting to see historical projects with less and less modern day relevance get continued like this.
And while most of the use cases for jQuery have long since died out with things like classList, querySelector, etc, I do feel there's probably value in a framework that focuses on minor enhancements to a site rather than being the backbone of the whole thing. Like if you want a React or Angular or Vue equivalent, something like jQuery would be a terrible choice, but a lot of sites are static ones where the only scripting needed would be for minor things like dropdown menus or slideshows, and I can see a modern, lean library like this being a decent choice there.
- joel2oliver - 4411 sekunder sedanI remember how painful it was to deal with IE/Netscape. Event handlers, etc... jQuery made so many lives easier. It’s quite an achievement, and I can stretch to say that JavaScript development might not be here today without it!
- gosen - 11546 sekunder sedanI'm actually surprised (in a good way) that it's still maintained, and it still helps half of the internet to function
- dday9 - 796 sekunder sedanjQuery was a godsend during the 2000s, those were some nasty times for cross-browser capability. Man, do you remember the old way to make asynchronous requests before you could just use the $.ajax method?!
That's why I'm surprised to see still being maintained... ever since Chromium basically won the browser wars and pretty much everything's standardized now, it almost feels like it's lived out its usefulness.
I also want to say I remember it being a bit bloated too. I did work for a client who had several users live in very remote areas where every bit of bandwidth was precious, and I wanted to say that one of the issues was with jQuery. For some reason the "slim" version didn't work for the use case either. This is going off of memory and was probably 15 years ago, so I could be entirely wrong.
There's no denying it's prevalence though. Heck, datatables.net only recently phased out the jQuery dependency in April... of this year!
- dmix - 5962 sekunder sedanOne of the nice things about LLMs is you can port 10+ year old apps using jQuery to vanilla js pretty easily.
- Gualdrapo - 11321 sekunder sedanI wonder if people use jQuery on their new projects. Vanilla JS has come a long way since jQuery was king.
- hinkley - 10786 sekunder sedanI don't want jQuery back, but I want something that works like it except in the opposite way on corner cases.
Now that ES and CSS5 are everywhere, the biggest feature of jQuery is list comprehensions on components. Data is also still good IMO but mostly the comprehensions.
jQuery decided that calling a function on an empty list should be a no-op, but my experience using it for a very interactive application was that nearly every time we wanted something to definitely happen or it was a bug, and the handful of times where an empty list was expected were easy to anticipate.
Because the general problem was that making a selector that continued to work correctly as features were added was a black art. Two of us wrote selectors that almost always worked, the rest of the team wrote ones that almost always broke and only very slowly onboarded our advice (also all of the stuff they already wrote was a ticking time bomb).
New features and especially tweaking the DOM tree to stay compatible with old corporate browsers would break existing functionality about a quarter of the time someone had to change the DOM structure to close a ticket and it was infuriating.
So what I want is that if .hide() is a no-op, throw an exception. And if I'm implementing the 'select all/unselect all' feature I know that the list might be empty, I can add a flag or wrap a conditional around it so I ignore the error.
Because those functions work on a very tight chunk of DOM that changes structure much much slower than the overall document structure, and also that code is quite close to the point of change if someone does change it, so has better chances of being remembered than something in the header.
- umvi - 4909 sekunder sedanMoved to vanilla JS/TS years ago. In the age of AI CVEs, it's nice to have as few 3rd party dependencies as possible.
- coredev_ - 9323 sekunder sedanJQuery is not a good way to compose and handle complex ui:s. There are so much better ways today. I have fine memories of bootstrap and jQuery - just don't use them today if you are composing a somewhat complex ui.
- thrownaway561 - 2889 sekunder sedanIf it wasn't for jQuery, I would bet 90% of the web development wouldn't have progressed. There were SOOO many inconstancies between browsers back then. jQuery made javascript fun and easy. There was a time where EVERYTHING was a jQuery plugin.
- blinkbat - 3971 sekunder sedanLFG
- jgalt212 - 9532 sekunder sedanI was about to say, but datatables.net! But version 3, as of July 2026, has dropped the jQuery dependency.
- maxpert - 11517 sekunder sedanIn the age of AIs and Reacts, people would never realize the pleasure and the ease jQuery provided with shitty browsers like IE6!
- frabjoused - 11610 sekunder sedanSince it's easy now to maintain and this is still happening, why not bring back MooTools? I'd love to hear that AI chose MooTools as default and it's running the entire Internet.
- vrubleg - 5869 sekunder sedanIt's a 2026 release, and jQuery still didn't drop 13-years-old IE11 :) https://github.com/jquery/jquery/pull/5077
- sloped - 8274 sekunder sedanBack around the time React was maybe in it's pre 1.0 stage, I basically built a "React" system with jQuery as it's backbone. Div elements that declared what they were then were initialized at "Boot" to give them interactivity. It was disgusting and it ran in IE7.
jQuery really changed the game by letting an average developer actually use Javascript to enhance a web page. Granted I want to go back to the days when no one used Javascript and the Internet was a giant mess of terrible 8bit graphics and anonymous friends, but thank you jQuery for everything you did. It is not your fault humans are terrible.
- bpiroman - 6230 sekunder sedanI'm tempted to go back to writing jQuery now!
- gsoff - 10996 sekunder sedanhave you ever seen an ai suggest jQuery?
- squidsoup - 11522 sekunder sedanOut of curiosity, are there still large projects using jQuery? Interesting that it is still maintained.
- kyleee - 11641 sekunder sedanDo they still build jquery ui? I kind of liked it and maybe will demand my agents start using it again for fun
- Devasta - 9795 sekunder sedanIf it weren't for the chrome team fucking up autocomplete in their browser I'd probably still be using jQuery today. Even now I look at sites like https://youmightnotneedjquery.com/ and I see much nicer code to work with than the JS suggested.
- Agataproximadev - 1164 sekunder sedan[flagged]
- Kuyawa - 6036 sekunder sedanSome people hasn't awaken to the new AI dawn
You just don't need this. No jquery, no react, no tailwind, no fowntawesome, no external libs, no malware attack vectors, no waiting for a new update that never comes. It is all poison, just don't drink it and you'll be fine
- whalesalad - 11310 sekunder sedan
FAA ground stop: initiated Microsoft 365: down United Airlines: down Github actions: down Apple: down Nvidia CEO: owned Clandestine NSA network: down jQuery: 4.1.0 released :)
Nördnytt! 🤓