I'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.
jQuery collections are much much nicer than the incredibly anemic NodeList you get from querySelector, which doesn't even implement a full JS Array. You can set states on every element matching a jQuery selector as if it were a single element. I don't personally use jQuery very often since I prefer declarative components, but if I'm whipping up something imperative like a user script, it's hard to beat jQuery's "lenses for the DOM", as one Haskell programmer put it.
> set states on every element matching a jQuery selector
Very much so. jQuery had 2 major selling points - (1) browser polyfills and (2) conciseness, as per their motto, "Write less, do more". It seems (2) has been largely forgotten since (1) has been rendered obsolete. Its idea of running functions on a collection often made scripts end up at one-third to one-half of the equivalent vanilla JS, which needs loops to do the same thing.
Love me some jQuery. I honestly think the web would be in a better place if we hadn't stopped using HS for things like little jQuery scripts and kept the servers doing the controllers and handling the models.
The inconsistent collection APIs are such an unhinged part of JS. You’re telling me Map doesn’t implement map()? I bet habitually using jQuery feels divine.
Serious question: On modern hardware how much performance is jQuery actually taking away from you? Compared to the ridiculous overkill factor of using React for simple static pages, a practice I see everywhere now, the time it takes jQuery to parse seems inconsequential.
Not sure about "modern hardware" but I think the comparison is between jQuery vs. Vanilla JS on "modern browsers".
My only data point was my Blog felt significantly snappier on my 5 year old phone - especially on bad 4G connections - when i simply ditched jQuery and used Vanilla JS.
> The latest version of jQuery (v4.0.0) is 76.8 kB minified and 27.0 kB minified + gzipped.
More than you'd think if you start looking outside of the western tech bubble. Not everyone across the whole globe can afford the latest and greatest phones or laptops.
jQuery 3.8.0 was also part of this release (if "as a send-off, not a comeback" per the announcement[1]), and it supports IE 9-10, legacy Edge, iOS 7+, and Android 4.0+.
We just had a T1 line blow up the entire US air control infrastructure, so I'll happily assume people are still using old garbage in critical workflows.
Valid questions. In jQuery's case it's still so widely used by older codebases that it makes sense to improve and keep maintained. I think it's important to have alternatives in any case. Some people still prefer to write code by hand, and some people prefer jQuery.
Same reason we've always sacrificed performance for syntactic sugar. Readability and maintainability are the big ones. If you trust your AI to get it right, sure I guess that doesn't matter.
>I wonder how many websites on the web still use jquery today
Probably more than use React, by total domains alone. It's a bit like WordPress; so ubiquitous you forget it's even there, and with a long tail that will outlive many people reading this.
yup. we still had it on every page at my last job, even though it was a 100% React frontend (literally - even things like error pages were done with JSX for some reason!) merely because when the first parts of the site were written, they used $.ajax instead of fetch for some reason, and they never wanted to refactor anything.
fetch only became available in 2015 and it was awhile before it was commonly supported. At the time, jQuery's ajax was much nicer than handling the XMLHttpRequest yourself. I have sites that have gone through all three, finally replacing $().ajax with fetch only in the last couple years.
well its actually ship by wordpress, although not turned on my default, most themes and plugins do. So that already makes up for a huge part of the internet.
Although 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.
To that point, there was a conscious choice that the return type of most method invocations (except in specific "read a value" modes) should be a standardized container type.
That was, and still is, rare! And in a time without type checking and bundling, it was vital. Match your parentheses and quotes, and your jquery code might not find what you want, but it would (likely) not throw exceptions.
As I understand it, it's a different method to create something that matches the whole idea of a fluent interface, without having to build every method to support chaining, isn't it? And in a way that works for all language features rather than just your custom methods?
Maybe not precisely the same from a technical point of view but is it just pendantry to argue against someone referring to it as a fluent interface? Happy to learn and to be corrected if required.
I 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!
Sure, Netscape was dead (besides the name) before then. But in 2006 we were dealing with Gecko (mainly in the form of Firefox), IE6, IE7 which was brand new and most notable for being different than both IE6 and standards-compliant browsers, and Safari.
Yes. I did not so long ago. Vanilla JS is fine in term of features, but if you consider jQuery code idiomatic, then it's much more compact and readable for some development patterns.
> I wonder if people use jQuery on their new projects.
I do frequently, partially because I tend to branch new projects from old ones, and the old ones often used jQuery. Updating everything to vanilla would be a lot of effort for little gain.
I wonder how it feels for the original jQuery developers. They solved some big problems, then their ideas were just copied into Javascript itself, and their pioneering library became decried as old and irrelevant--even though it works just fine, and still solves some niche problems.
I'd use jQuery if IE11 support was a requirement. It's been a long time since I've seen that as a requirement, but IE11 was the last Internet Explorer before it got replaced by Edge. I wouldn't be surprised if there were hold-outs out there still using it...
I had to check wiki, IE 11 came out 13 years ago! Internet Explorer 11 support ended on June 15, 2022, and it was permanently disabled on February 14, 2023. ( must have missed the memo or I have forgotten about it )
W3Counter shows Around 0.07% of market share.
I wonder why IE11 is still being used or even a requirement? Especially in today's world where security could be a very serious issue.
IE 11 isn't fully out of support for a few more years yet. There are so many enterprises using it with so many custom tools built just for the browser. Most is tight lipped under NDAs but some of the details and remaining usage figures are staggering.
I do when absolutely necessary, which is becoming rarer as Vanilla JS improves, like you stated. One of my coworkers is still using it on all new projects though. My employer has avoided the whole SPA scene for better or worse.
Go ahead, use document.querySelector. Why? Because chaining and a bunch of other stuff and not bothering to check if querySelector actually got anything every single time. Vanilla JS is like bringing a knife to a gun fight.
There's a purpose for everything. Jquery is quite nice to write and works great. For a whole site, I'd these days be interested in building with HTMX, but JQ is fine and has the advantage that there are millions of people out there who know it well.
What vanilla is obviously unbeatable for is, you're writing a snippet of JS that you can hand anyone[1] to run with no dependency requirements. Some codebases may be explicitly incompatible with JQ, so knowing how to do all the JQ basics "vanilla" is an important skill so you don't have to bring in a "big" (relatively, I mean) library to support a 7-line function.
[1] for example, an embed code, an analytics tag, or a script to customize the markup on a page.
I 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.
If 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.
JQuery 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.
Bootstrap has been effectively replaced by Grid/Flex. There is no need for it.
There is a ton of stuff you can do now with JS directly that JQuery had to compensate for, that's why GitHub spent the effort to move off of JQ years ago.
CSS and JS has come a long way. I will even venture out to say that UI development does not suck these days, it's even a little enjoyable. You no longer have to spend 3 hours vertically aligning text in a div and then test it in four different browsers.
Since 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.
Back 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.
Frontend legacy is especially difficult to refactor away from. So many edge case visual regressions and browser compatibility issues make end to end verification really hard. It makes sense jQuery is still so popular in legacy monoliths
Seeing Wordpress isn't a shock since JQuery comes bundled directly with it by default. You have to remove it manually if you don't want it. Add in a majority of themes, page builders and themes rely on JQuery for interactivity and DOM manipulation.
Until people stop making sites with Wordpress, JQuery will continue to live on for a while.
I was there, Gandalf, I was there the day the strength of Men failed.
The three biggest problems with JQuery UI:
1) The quality wasn't anywhere near as good as jquery, so many times I had to correct people whose opinion of jquery encompassed jquery UI
2) They declared bankruptcy on managing the call tree spaghetti and decided to rewrite the entire thing one component at a time, which meant that simultaneously some things were changing a lot and everything else they refused to entertain bug reports on the parts that were still in the queue.
3) It took them three times as long to do the work as they expected, and the original ask was already a bit much.
Angular became a thing before they finished the work.
I never got the sense that Elrond hated his own ancestry. Certainly not as Tolkien wrote it, though maybe the movies inserted it? He chose to follow the elven path; his brother chose the other. There was sadness between them, but no animosity - same for his daughter.
If 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.
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
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 :)
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.
Very much so. jQuery had 2 major selling points - (1) browser polyfills and (2) conciseness, as per their motto, "Write less, do more". It seems (2) has been largely forgotten since (1) has been rendered obsolete. Its idea of running functions on a collection often made scripts end up at one-third to one-half of the equivalent vanilla JS, which needs loops to do the same thing.
When most code is and will be written by AI, why would I sacrifice performance for syntactic sugar?
My only data point was my Blog felt significantly snappier on my 5 year old phone - especially on bad 4G connections - when i simply ditched jQuery and used Vanilla JS.
> The latest version of jQuery (v4.0.0) is 76.8 kB minified and 27.0 kB minified + gzipped.
We just had a T1 line blow up the entire US air control infrastructure, so I'll happily assume people are still using old garbage in critical workflows.
1: https://blog.jquery.com/2026/11/17/jquery-4-1-0-and-3-8-0-re...
Approximately 64% of all websites—or roughly 67 million live domains—currently use jQuery.
Probably more than use React, by total domains alone. It's a bit like WordPress; so ubiquitous you forget it's even there, and with a long tail that will outlive many people reading this.
That was, and still is, rare! And in a time without type checking and bundling, it was vital. Match your parentheses and quotes, and your jquery code might not find what you want, but it would (likely) not throw exceptions.
For those unfamiliar, I recommend looking at https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast... and searching for the 201 instances of
in that file. A remarkably fluent API. We could all be so elegant.A TC39 Stage 2 proposal adds this into the language itself with the pipeline `|>` operator. [2]
[1] https://en.wikipedia.org/wiki/Fluent_interface
[2] https://github.com/tc39/proposal-pipeline-operator
Maybe not precisely the same from a technical point of view but is it just pendantry to argue against someone referring to it as a fluent interface? Happy to learn and to be corrected if required.
jQuery made the decision to do this, not JavaScript.
I do frequently, partially because I tend to branch new projects from old ones, and the old ones often used jQuery. Updating everything to vanilla would be a lot of effort for little gain.
I wonder how it feels for the original jQuery developers. They solved some big problems, then their ideas were just copied into Javascript itself, and their pioneering library became decried as old and irrelevant--even though it works just fine, and still solves some niche problems.
W3Counter shows Around 0.07% of market share.
I wonder why IE11 is still being used or even a requirement? Especially in today's world where security could be a very serious issue.
What vanilla is obviously unbeatable for is, you're writing a snippet of JS that you can hand anyone[1] to run with no dependency requirements. Some codebases may be explicitly incompatible with JQ, so knowing how to do all the JQ basics "vanilla" is an important skill so you don't have to bring in a "big" (relatively, I mean) library to support a 7-line function.
[1] for example, an embed code, an analytics tag, or a script to customize the markup on a page.
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.
There is a ton of stuff you can do now with JS directly that JQuery had to compensate for, that's why GitHub spent the effort to move off of JQ years ago.
CSS and JS has come a long way. I will even venture out to say that UI development does not suck these days, it's even a little enjoyable. You no longer have to spend 3 hours vertically aligning text in a div and then test it in four different browsers.
jQuery returned useful collections. DOM methods return an anemic NodeList which doesn't even implement Array interface.
Very beautiful.
BTW, browsers didn't even add forEach to it until several years after they added document.querySelectorAll lol
Edit. https://caniuse.com/?search=nodelist
NodeList appeared in 2006(Firefox) - 2008 (Safari) - 2010 (Chrome)
forEach on it appeared in... 2016.
https://datatables.net/blog/2026/datatables-3
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.
So often was the case that the two ran together, especially with IE6.
There's a list of large legacy sites that use jquery behind that link, including:
* Microsoft.com * Pinterest.com * Adobe.com * Yahoo.com * Wordpress.org * Digicert.com * Samsung.com * Archive.org
Until people stop making sites with Wordpress, JQuery will continue to live on for a while.
The three biggest problems with JQuery UI:
1) The quality wasn't anywhere near as good as jquery, so many times I had to correct people whose opinion of jquery encompassed jquery UI
2) They declared bankruptcy on managing the call tree spaghetti and decided to rewrite the entire thing one component at a time, which meant that simultaneously some things were changing a lot and everything else they refused to entertain bug reports on the parts that were still in the queue.
3) It took them three times as long to do the work as they expected, and the original ask was already a bit much.
Angular became a thing before they finished the work.
Unrelated, but it blew my mind when I learned that Elrond is half-man.
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