The composability of jQuery has been an inspiration for the way I design my own frameworks and tools.<p>One thing I still regularly use jQuery for, though, that's rarely mentioned, is its event model. You can put a listener on any object, not just things in the DOM. Any data object can trigger an event. This is incredibly powerful for isolating logic from DOM elements and events. A frequent use case is for DOM elements to contain a reference to a data object that may be replicated elsewhere on the page. The data object sets up and tears down visual elements, listening for interaction, then dispatches a custom event. Your core logic listens for events on the data object instead of on every individual element that might refer to it. I usually delegate the draw routine for e.g. html snippets of a card or an interactive element to the data object itself in a draw() function that returns a string which incidentally jQuery handles quite nicely inserting into the DOM without needing to explicitly call createElement.<p>I wrote my own implementation of this a long time ago, but in the end, that feature plus the other ergonomics of jQuery still make it my go-to today over vanilla js. And pretty much everything I write is without any reactive framework (other than my own vanilla component/templating/remoting system), so the overhead is barely noticeable.
> The composability of jQuery has been an inspiration for the way I design my own frameworks and tools<p>Not just as a framework but its documentation is also probably an inspiration for later libs. It was the first site for me where you could see the code and result together on the same page at the same place. And the discoverability of widgets was also great and exciting in a way.<p>Just open the firebug console, and try the examples for selectors, callbacks etc.
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.<p>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.<p>For those unfamiliar, I recommend looking at <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/jquery/JQuery.d.ts" rel="nofollow">https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...</a> and searching for the 201 instances of<p><pre><code> : this
</code></pre>
in that file. A remarkably fluent API. We could all be so elegant.
This is one of the first things I learned in programming. A friend back in University showed me a bit of his code (neither of us were in CS), and I was like why are you returning `this`? Then he showed me this chaining. I only found it a "cool trick" at the moment, who'd told me that I'd end up loving it the more I learned programming. I've made two of my main libraries, `umbrellajs` and a plumbing one called `swear` (chaining but for promises, some chaining syntax sugar on top of promises basically), based on this. I stopped doing it too much in recent years, but still it's amazing.
If you pick a pure OOP language like Ruby, you'll have the same experience. You can pick a literal and call a method on it and chain the method calls. It's lovely.
Mootools was way better but never got the attention jquery got.
Meh, other than being easier to type, it's nothing to sing praises about. It is harder to reason about, both for the interpreter (which does not immediately know that the return value is the same object as the receiver and therefore cannot optimize based on that assumption) and for the programmer (which has to look up documentation to learn the same).<p>I hope <a href="https://github.com/tc39/proposal-pipeline-operator" rel="nofollow">https://github.com/tc39/proposal-pipeline-operator</a> and perhaps also <a href="https://github.com/tc39/proposal-do-expressions" rel="nofollow">https://github.com/tc39/proposal-do-expressions</a> will put it to rest.
Why? It's still the sanest choice for a site that doesnt need a bloated js "framework".
Things like Alpine, HTMX, and Datastar seem to be more in favor these days.<p>They have the small surface area of jQuery, but still aim for component-based reactivity and SSR-when-possible which just aligns more with the mental model and development preferences that have developed from the whole world of React/Next and similar.
This is called a fluent interface. [1] C++ streams are perhaps the most common example of this pattern.<p>A TC39 Stage 2 proposal adds this into the language itself with the pipeline `|>` operator. [2]<p>[1] <a href="https://en.wikipedia.org/wiki/Fluent_interface" rel="nofollow">https://en.wikipedia.org/wiki/Fluent_interface</a><p>[2] <a href="https://github.com/tc39/proposal-pipeline-operator" rel="nofollow">https://github.com/tc39/proposal-pipeline-operator</a>
Not very relevant? It's still powering 64% of the websites in the world in 2026. React is only powering about 6% of the websites in the world today.<p>Jquery is only not relevant if you're living in a tech bubble that demands that "new, shiny" is the only thing that could possibly be relevant.
Where are those numbers from, I make it about 53% and 10% for react. <a href="https://theweb.report/#front-end" rel="nofollow">https://theweb.report/#front-end</a><p>But still everywhere!
True. I am living in such a tech bubble. It has been a very long time since I've worked with jQuery. Which is separate from my personal feelings about jQuery, since I'm a jQuery fan - although these days I wouldn't use it, since changes in Web APIs, changes partly inspired by jQuery, have made it possible to write jQuery-esque code without actually loading jQuery.
amen
Are you talking about method chaining, something that comes from JavaScript (technically the DOM I suppose), not jQuery?
Method chaining is library-specific, a function of methods returning `this`/`self`.<p>jQuery made the decision to do this, not JavaScript.
Yes, I'm talking about using JS' method chaining. That's what I mean by "going with a language's features".
It was not commonplace at the time jQuery was released.
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.<p>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.
<i>> set states on every element matching a jQuery selector</i><p>Very much so. jQuery had 2 major selling points - (1) browser polyfills and (2) conciseness, as per their slogan, "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.
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.
That's a lot of stuff just for [...nodeList].
There is a heap of indie devs that swear by jQuery and avoid the frameworks like react. Each has their use cases.
I think Datastar probably fits that idea the best in terms of "mild interactive enhancements".<p>It's sort of the same sort of less-is-more mindset of jQuery but for the modern reactive-component model - intentionally small, allows SSR swapping when possible (like HTMX), and adds the layers of reactivity that can still only be reasonably done with frontend scripting.
I would probably use Hyperscript for that use case: <a href="https://hyperscript.org/" rel="nofollow">https://hyperscript.org/</a>
I wonder how many websites on the web still use jquery today
StackOverflow still does. Delivered via Google for no good reason other than to give them tracking data on SO users.
A lot actually
If you believe a google query:<p>Approximately 64% of all websites—or roughly 67 million live domains—currently use jQuery.
>I wonder how many websites on the web still use jquery today<p>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.
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.
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.
That’s gotta be it. I think the older parts of the codebase definitely either predated 2015 or straddled the time where you couldn’t assume fetch was there. And I agree, XHR was actually pretty absurd, having used it in about 2006 before discovering JQ.
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!
I'm actually surprised (in a good way) that it's still maintained, and it still helps half of the internet to function
I don't think I'd reach for jQuery ever again, but I'd used it extensively fifteen years ago. I'm glad it's still alive and kicking. When it's already in a project that I'm making changes to, it's a cute way to do stuff easily that would be a pain with vanilla dom.
jQuery 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?!<p>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.<p>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.<p>There's no denying it's prevalence though. Heck, datatables.net only recently phased out the jQuery dependency in April... of this year!
Those original AJAX API's were pretty slick, but not well understood at the time. Surprisingly they could stream characters! The response is partially available each time onprogress fires:<p><pre><code> const xhr = new XMLHttpRequest();
let lastLength = 0;
xhr.addEventListener("progress", () => {
const chunk = xhr.responseText.substring(lastLength);
lastLength = xhr.responseText.length;
console.log("New data:", chunk);
});
xhr.open("GET", "/stream");
xhr.send();
</code></pre>
-------------------<p>The modern fetch API is better though because it's a Promises API and it can stream as raw bytes, not characters:<p><pre><code> const response = await fetch("/stream");
const reader = response.body.getReader();
while (true) {
const { value, done } = await reader.read();
if (done) {
console.log("Finished");
break;
}
console.log("Received", value.length, "bytes");
}</code></pre>
It's actually a little easier these days:<p><pre><code> const response = await fetch("/stream");
for await (const value of response.body) {
console.log("Received", value.length, "bytes");
}
console.log("Finished")</code></pre>
[dead]
One of the nice things about LLMs is you can port 10+ year old apps using jQuery to vanilla js pretty easily.
I wonder if people use jQuery on their new projects. Vanilla JS has come a long way since jQuery was king.
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>I wonder if people use jQuery on their new projects.</i><p>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.<p>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 )<p>W3Counter shows Around 0.07% of market share.<p>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>> permanently disabled</i><p>Only on Windows 10 and 11. It still runs as it always did on previous Windowses.
I do because every time I try to use vanilla JS, I end up reinventing the $ function and adding a few basic utilities, at which point it feels like I might just use jQuery and make my code more compact and legible.<p>That being said it's no longer that useful for dealing with browser incompatibilities or for remote calls. I end up using a stripped version or something like <a href="https://github.com/fabiospampinato/cash" rel="nofollow">https://github.com/fabiospampinato/cash</a>
It is still less verbose than the DOM navigation APIs that landed on the browsers.
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.<p>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.<p>[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.<p>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.<p>jQuery decided that calling a function on an empty list should be a no-op, but my experience using it for a <i>very</i> 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.<p>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).<p>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.<p>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.<p>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 <i>does</i> change it, so has better chances of being remembered than something in the header.
Moved to vanilla JS/TS years ago. In the age of AI CVEs, it's nice to have as few 3rd party dependencies as possible.
I still wish jQuery kept at least 2 years of browser support, rather than last 3 versions of iOS, or 2 of Firefox. Many people are stuck on old iOS.
Used it extensively 15 years ago, at the start of my career.<p>Did not know this library is still being maintained
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.
Legendary drop, so many great memories
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.
In the age of AIs and Reacts, people would never realize the pleasure and the ease jQuery provided with shitty browsers like IE6!
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.
It's a 2026 release, and jQuery still didn't drop 13-years-old IE11 :)
<a href="https://github.com/jquery/jquery/pull/5077" rel="nofollow">https://github.com/jquery/jquery/pull/5077</a>
The little library that took on $.
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.<p>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.
I'm tempted to go back to writing jQuery now!
have you ever seen an ai suggest jQuery?
LFG
I was about to say, but datatables.net! But version 3, as of July 2026, has dropped the jQuery dependency.<p><a href="https://datatables.net/blog/2026/datatables-3" rel="nofollow">https://datatables.net/blog/2026/datatables-3</a>
Out of curiosity, are there still large projects using jQuery? Interesting that it is still maintained.
Yes, about 63% of all websites: <a href="https://w3techs.com/technologies/details/js-jquery" rel="nofollow">https://w3techs.com/technologies/details/js-jquery</a><p>There's a list of large legacy sites that use jquery behind that link, including:<p>* Microsoft.com
* Pinterest.com
* Adobe.com
* Yahoo.com
* Wordpress.org
* Digicert.com
* Samsung.com
* Archive.org
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.<p>Until people stop making sites with Wordpress, JQuery will continue to live on for a while.
Surely, I thought, cPanel/WHM no longer use jQuery, right? But it seems they might?? <a href="https://api.docs.cpanel.net/guides/guide-to-cpanel-interface-customization-and-branding/guide-to-cpanel-interface-customization-jquery" rel="nofollow">https://api.docs.cpanel.net/guides/guide-to-cpanel-interface...</a>
Do they still build jquery ui? I kind of liked it and maybe will demand my agents start using it again for fun
I was there, Gandalf, I was there the day the strength of Men failed.<p>The three biggest problems with JQuery UI:<p>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<p>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.<p>3) It took them three times as long to do the work as they expected, and the original ask was already a bit much.<p>Angular became a thing before they finished the work.
> I was there, Gandalf, I was there the day the strength of Men failed.<p>Unrelated, but it blew my mind when I learned that Elrond is half-man.
I either somehow missed that, or forgot. So... today is the day <i>I</i> learned
I don't know if that was his Hitler dig or just a common trope, of people hating their own ancestry.
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.
Elrond never hated his ancestry.
Maintenance mode, but there have been some updates. Announcement: <a href="https://blog.jqueryui.com/2021/10/jquery-maintainers-update-and-transition-jquery-ui-as-part-of-overall-modernization-efforts/" rel="nofollow">https://blog.jqueryui.com/2021/10/jquery-maintainers-update-...</a>
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 <a href="https://youmightnotneedjquery.com/" rel="nofollow">https://youmightnotneedjquery.com/</a> and I see much nicer code to work with than the JS suggested.
[flagged]
[flagged]
Some people hasn't awaken to the new AI dawn<p>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
Sounds maintainable.
[dead]
<p><pre><code> 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 :)</code></pre>