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.
He seems to be awfully done with humans. Not round them up done, but stay the fuck over there and leave us alone done for sure. Oh you're all dying? That sucks for you.
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.
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.
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.
The problem with jQuery is that it swallows all errors. Dead code remains and you're none the wiser. That's only ok if you ship 2 KB of JS, at which point You Might Not Need jQuery either.
$('.mispell').hide()
No error. Just silent. This is why jQuery is not a good library other than for 2010 cross-browser development.
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.
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.
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 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.
John Resig et al scattered some corn and they ate them like chickens. They stole the ideas and couldn't copy the features adequately. They had one job. They failed. They should've brought a black suitcase full of money to them and ask nicely to implement the whole thing to replace the abhorrent JS browser side implementation.
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.
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 https://github.com/fabiospampinato/cash
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 :)
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.
I don't feel like it should be a feature of `hide`, sounds like it should be a feature of the element-finding methods (`$`, `find`...). If instead of `find` you had `maybeFind` and `findOrThrow`, you wouldn't have these issues.
You can "just" add these methods and ban raw `find` with linting?
The two replies I've gotten remind me of the sentiment of C developers who panned Java as being ridiculous because you could just do garbage collection in C if you wanted to.
There's a lot of things you can do when you're a sole proprietor on a project. But other developers have opinions and they expect them to be respected as much as you expect them to respect yours.
Can you think of the last project where you got everything your way? I can't, and I have a reputation of being pretty insistent about people trying my suggestions before they say no.
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.
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.
I considered doing it in my top-level comment but I decided not to, since I don't actually know enough about monads to be sure that I know what I'm talking about, lol.
Well, jQuery is how I got introduced to the concept of monads. After that I picked up Haskell, then Elm and Purescript, which allowed me to use the monads the way functional gods intended to... Web scale!
That'd be an interesting alternative reality!
What ended up happening is that I'm writing (having it written by agents) react like everybody else.
Parent poster here, for some reason I never made the connection - but of course jQuery is a monad in the way that Railway Oriented Programming (https://fsharpforfunandprofit.com/rop/) is - which is to say, the thing on which side effects are done, in this case the DOM, is implicit, but in many other ways we're just binding things into a chainable system!
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.
paulddraper has phrased it perfectly in answer to your previous post - chaining everything so that the process flow reads fluently from left to right. (I'm replying just to avoid leaving your question hanging.)
To suggest the pipeline proposal must not be referred to as a "fluent interface" would seem to me to be arguing semantics, ignoring the point behind the words, or the facts that they can have implied meanings or subtle changes over time.
I think the point behind the words is that it is a specific design pattern based on building DSLs using method chaining. I don't think pipelines, broadly, are an implementation of that design pattern. It's a way to string together function calls in a way that they read left-to-right, yes, but the spirit of "fluent interface" is not just "reads left-to-right." It's a specific pattern.
Isn't the point of a fluent interface that all functions (or methods) return the same interface, thus allowing for the desired chaining?
And obviously, this is a design pattern that fits when a suitable supertype exists or xan be easily defined.
Thus, void methods are already fit for pretty much the same interface, and everything with a return value that shouldn't be of the type of that specific god-interface, doesn't fit well into a fluent interface, e.g. count().
You can be insistent on the pattern and make count() return `this` instead of a number, but that's where the pattern becomes blurry.
When I started web dev, fluent interfaces were everywhere, and the motivations, thinking about it, seem to converge about another, different thing: lazy evaluation.
This is what jQuery has in common with ORMs, I'd guess.
The development experience isn't even the most important thing, it's providing an abstraction between executing a query (hence jQuery) and chaining selectors.
Natrowing down snapshots is completely different from chaining selectors, and this is the common aspect between an ORM and a library working on the DOM.
Where it starts to feel icky, in both cases, is, when mutations are involved.
Then you have potential for confusion around when these mutations are commited.
In other words, since jQuery collections are, well not "live", like getElementsByTagName, also not snapshots, like querySelectorAll is (snapshot regarding the reference, not what it points at, of course).
jQuery combined the best of both worlds for many everyday applications.
But mentally working through an applications with complex mutations only was fun if your colleagues were disciplined.
jQuery "soup" when using many mutations, leveraging the DOM as a snychronized shared state, and mixing in some confusing closures anf loops, was also real.
I admire jQuery, but also don't miss debugging half-working giant files. Not a library issue, you can have similar issues with any library when working on dynamic frontend state.
Circling back to the point: I'm not sure whether a fluent
interface is ideal for DOM manipulation.
But in any case, jQuery was used way beyond "DOM library". It was almost synonymous with "JavaScript" at some point, and putting huge blocks of imperative domain logic nested 5 closures deep into some event callback was an issue with jQuery just as it is an issue with React right now.
(ignore that some of these should be chained and some should be arguments, I haven’t read the proposal fully)
They’re doubly nice in Clojure because of the lazy evaluation. You can map a pipeline over a list and it will evaluate one at a time rather than pre-evaluating and allocating memory for the whole thing.
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).
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.
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.
Things like Alpine, HTMX, and Datastar seem to be more in favor these days.
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.
Given how good AI is at coding, I'd be tempted to just have it write vanilla Typescript that uses direct DOM manipulations unless I really wanted to leverage a framework's ecosystem of components.
Sure, but the point of any library really is to provide a consistent way of doing things.
Datastar is quite a small library and all it is doing is giving you a nice repeatable way to organize the stuff you’ll do with your TypeScript slop.
If you intentionally don’t use a library or framework, humans generally eventually reproduce one, often very poorly.
AI doesn’t even try, it just slops and barfs and writes until something works
Why would a site that does not need a bloated js framework need jQuery? What is it that jQuery brings to the table that is worth paying for in terms of making it a dependency?
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.
It’s still probably the most distributed library. Every Wordpress site includes it.
I had to use it on a legacy site recently and forgot how nice it was and it all just came back to me too. Didn’t need docs either. That’s a sign of a very well designed lib
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.
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.
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.
>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.
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.
Yeah. And also, 2015 was the same time when Promises became part of the spec. That was the justification for fetch in the first place. Now that we have this ability to do asynchronous stuff, and everyone is writing these hairy XHMLHttpRequests listening for 200s and 400s, let's just make this a standard thing. It was a good idea. So, $().ajax still handled its results with callbacks, it wasn't async, didn't need a shim for that, although it was easy enough to wrap. You wouldn't necessarily replace it until you were ready to rewrite a whole bunch of other stuff in your code with async functions. For me, a bigger question for older code was transitioning the bulk of the code to promise patterns, even though I would've otherwise wanted to swap fetch for ().ajax much sooner.
[edit] I just checked, and I still have one major production site whose backend calls still run:
`let req:XMLHttpRequest = new XMLHttpRequest();
req.onreadystatechange = ()=> {`
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.
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.
But you don't need the latest and greatest phone to have the latest browser. Android 10 (released in 2019) supports the latest chromium versions and android 8 (2017) and 9 (2018) support up to v138.
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.
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.
jQuery feels much snappier than React, and vanilla JS feels much snappier than jQuery. There is genuinely a noticeable different even in fairly simple UIs.
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 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.
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.
jQuery had a lot of reasons for existing. And now it has less than it used to. I believe that was the point.
You'd probably usually chain that inside the callback. Instead of addClass('foo').hide(), you'd do el.classList.add('foo'); el.hidden = true; or something. It's not 1:1, but also it's not really that big a deal.
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.
I think Datastar probably fits that idea the best in terms of "mild interactive enhancements".
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.
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
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.
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 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!
JQuery 4.1 is 78k minified, and 25k after Brotli compression. I'd venture a guess that 90% of the images on any given site are larger than all of JQuery. I wouldn't consider it bloated.
I think you misunderstood or read past what I was saying.
I wasn't talking about version 4.1, this would have been version 1.x (maybe 1.5... it was ~15 years ago), and the issue was bandwidth usage for uber remote users. There were all sorts of tricks I remember implementing to get that project over the finish line, but one of them was definitely yoinking jQuery out of the project, despite me being a big advocate for the library.
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:
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.
The composability of jQuery has been an inspiration for the way I design my own frameworks and tools.
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.
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
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.
Just open the firebug console, and try the examples for selectors, callbacks etc.
Man, just seeing the name jQuery took me back to the days I was using MooTools for its fantastic animation engine and was always annoyed how simpler jQuery was to implement while mootools was superior for front end design. Thanks for the memory lane.
kyleee | 22 hours ago
hinkley | 22 hours ago
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.
simlevesque | 22 hours ago
Unrelated, but it blew my mind when I learned that Elrond is half-man.
booty | 22 hours ago
simlevesque | 21 hours ago
hinkley | 22 hours ago
eszed | 21 hours ago
sigzero | 20 hours ago
hinkley | 18 hours ago
LVB | 22 hours ago
askbjoernhansen | 22 hours ago
dasil003 | 22 hours ago
gnabgib | 20 hours ago
dasil003 | 18 hours ago
LVB | 19 hours ago
frabjoused | 22 hours ago
maxpert | 22 hours ago
wuhhh | 22 hours ago
djfobbz | 21 hours ago
gosen | 22 hours ago
squidsoup | 22 hours ago
ddalcino | 22 hours ago
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
buildwrangler | 22 hours ago
burningChrome | 21 hours ago
Until people stop making sites with Wordpress, JQuery will continue to live on for a while.
bluepeter | 21 hours ago
maxpert | 22 hours ago
coffeefirst | 22 hours ago
W3cUYxYwmXb5c | 22 hours ago
masklinn | 21 hours ago
Gualdrapo | 22 hours ago
elondaits | 22 hours ago
etatester | 5 hours ago
$('.mispell').hide()
No error. Just silent. This is why jQuery is not a good library other than for 2010 cross-browser development.
hirvi74 | 22 hours ago
bryanlarsen | 22 hours ago
ksec | 21 hours ago
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.
OuterVale | 20 hours ago
abanana | 19 hours ago
Only on Windows 10 and 11. It still runs as it always did on previous Windowses.
pjmlp | 22 hours ago
petre | 21 hours ago
xp84 | 20 hours ago
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.
DamnInteresting | 20 hours ago
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.
lofaszvanitt | 16 hours ago
marticode | 17 hours ago
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 https://github.com/fabiospampinato/cash
pknerd | 12 hours ago
whalesalad | 22 hours ago
gsoff | 22 hours ago
squidsoup | 22 hours ago
flykespice | 22 hours ago
squidsoup | 22 hours ago
hinkley | 22 hours ago
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.
FartinMowler | 22 hours ago
williamdclt | 7 hours ago
You can "just" add these methods and ban raw `find` with linting?
hinkley | 6 hours ago
There's a lot of things you can do when you're a sole proprietor on a project. But other developers have opinions and they expect them to be respected as much as you expect them to respect yours.
Can you think of the last project where you got everything your way? I can't, and I have a reputation of being pretty insistent about people trying my suggestions before they say no.
Devasta | 22 hours ago
hax0ron3 | 22 hours ago
embedding-shape | 21 hours ago
kiliancs | 21 hours ago
tyre | 21 hours ago
jQuery made the decision to do this, not JavaScript.
hax0ron3 | 21 hours ago
btown | 21 hours ago
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.submain | 16 hours ago
hax0ron3 | 16 hours ago
lgas | 11 hours ago
classified | 3 hours ago
egeozcan | 2 hours ago
That'd be an interesting alternative reality!
What ended up happening is that I'm writing (having it written by agents) react like everybody else.
btown | 6 minutes ago
paulddraper | 21 hours ago
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
anamexis | 20 hours ago
abanana | 20 hours ago
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.
anamexis | 19 hours ago
abanana | 8 hours ago
To suggest the pipeline proposal must not be referred to as a "fluent interface" would seem to me to be arguing semantics, ignoring the point behind the words, or the facts that they can have implied meanings or subtle changes over time.
anamexis | 4 hours ago
moritzwarhier | an hour ago
And obviously, this is a design pattern that fits when a suitable supertype exists or xan be easily defined.
Thus, void methods are already fit for pretty much the same interface, and everything with a return value that shouldn't be of the type of that specific god-interface, doesn't fit well into a fluent interface, e.g. count().
You can be insistent on the pattern and make count() return `this` instead of a number, but that's where the pattern becomes blurry.
When I started web dev, fluent interfaces were everywhere, and the motivations, thinking about it, seem to converge about another, different thing: lazy evaluation.
This is what jQuery has in common with ORMs, I'd guess.
The development experience isn't even the most important thing, it's providing an abstraction between executing a query (hence jQuery) and chaining selectors.
Natrowing down snapshots is completely different from chaining selectors, and this is the common aspect between an ORM and a library working on the DOM.
Where it starts to feel icky, in both cases, is, when mutations are involved.
Then you have potential for confusion around when these mutations are commited.
In other words, since jQuery collections are, well not "live", like getElementsByTagName, also not snapshots, like querySelectorAll is (snapshot regarding the reference, not what it points at, of course).
jQuery combined the best of both worlds for many everyday applications.
But mentally working through an applications with complex mutations only was fun if your colleagues were disciplined.
jQuery "soup" when using many mutations, leveraging the DOM as a snychronized shared state, and mixing in some confusing closures anf loops, was also real.
I admire jQuery, but also don't miss debugging half-working giant files. Not a library issue, you can have similar issues with any library when working on dynamic frontend state.
Circling back to the point: I'm not sure whether a fluent interface is ideal for DOM manipulation.
But in any case, jQuery was used way beyond "DOM library". It was almost synonymous with "JavaScript" at some point, and putting huge blocks of imperative domain logic nested 5 closures deep into some event callback was an issue with jQuery just as it is an issue with React right now.
Same story, different day.
thaumasiotes | 3 hours ago
Note that the language with the best support for this concept is Perl, with its $_ variable.
everforward | 17 hours ago
|> docker.listContainers() filter(x => x.name == “something”) first getNetwork getIpAddress toString ping
(ignore that some of these should be chained and some should be arguments, I haven’t read the proposal fully)
They’re doubly nice in Clojure because of the lazy evaluation. You can map a pipeline over a list and it will evaluate one at a time rather than pre-evaluating and allocating memory for the whole thing.
paulddraper | 14 hours ago
Which true is not per se fluent interfaces, but it reads similarly.
And "fluent" -- as the name suggests -- has a lot to do with how it reads, left-to-right with no intermediate variables.
pwdisswordfishq | 19 hours ago
I hope https://github.com/tc39/proposal-pipeline-operator and perhaps also https://github.com/tc39/proposal-do-expressions will put it to rest.
leptons | 19 hours ago
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.
greenchair | 18 hours ago
hax0ron3 | 17 hours ago
addedlovely | 17 hours ago
But still everywhere!
hylaride | 3 hours ago
Software has a way of sticking around.
hk1337 | 18 hours ago
thallavajhula | 18 hours ago
lofaszvanitt | 16 hours ago
skrtskrt | 15 hours ago
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.
hax0ron3 | 13 hours ago
sgt | 10 hours ago
I'd still recommend keeping it at a minimum though. Rather rely on tools like htmx.
skrtskrt | an hour ago
If you intentionally don’t use a library or framework, humans generally eventually reproduce one, often very poorly.
AI doesn’t even try, it just slops and barfs and writes until something works
azangru | 10 hours ago
franciscop | 14 hours ago
pknerd | 12 hours ago
dawnerd | 10 hours ago
I had to use it on a legacy site recently and forgot how nice it was and it all just came back to me too. Didn’t need docs either. That’s a sign of a very well designed lib
jmathai | 12 hours ago
$('#selector').html('new <strong>text</strong>').attr('foo', 'bar');
jgalt212 | 22 hours ago
https://datatables.net/blog/2026/datatables-3
coredev_ | 22 hours ago
__abc | 22 hours ago
renegade-otter | 21 hours ago
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.
Kuyawa | 21 hours ago
troupo | 21 hours ago
jQuery returned useful collections. DOM methods return an anemic NodeList which doesn't even implement Array interface.
Kuyawa | 20 hours ago
troupo | 20 hours ago
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.
kuschku | 20 hours ago
edflsafoiewq | 20 hours ago
hajile | 17 hours ago
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
sloped | 21 hours ago
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.
tyre | 21 hours ago
So often was the case that the two ran together, especially with IE6.
CM30 | 21 hours ago
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.
liendolucas | 21 hours ago
Exoristos | 19 hours ago
liendolucas | 8 hours ago
proneb1rd | 21 hours ago
ramesh31 | 21 hours ago
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.
wouldbecouldbe | 21 hours ago
xp84 | 20 hours ago
noduerme | 20 hours ago
xp84 | 14 hours ago
noduerme | 10 hours ago
[edit] I just checked, and I still have one major production site whose backend calls still run:
`let req:XMLHttpRequest = new XMLHttpRequest(); req.onreadystatechange = ()=> {`
nchmy | 7 hours ago
kevin_thibedeau | 20 hours ago
sigzero | 20 hours ago
Approximately 64% of all websites—or roughly 67 million live domains—currently use jQuery.
cantalopes | 19 hours ago
dalemhurley | 21 hours ago
smt88 | 21 hours ago
When most code is and will be written by AI, why would I sacrifice performance for syntactic sugar?
reassess_blind | 20 hours ago
mathgeek | 20 hours ago
SoftTalker | 20 hours ago
smt88 | 19 hours ago
nilamo | 20 hours ago
saidinesh5 | 20 hours ago
TonyTrapp | 20 hours ago
smt88 | 19 hours ago
skydhash | 19 hours ago
majewsky | 19 hours ago
skydhash | 19 hours ago
Timon3 | 17 hours ago
nchmy | 7 hours ago
starkparker | 20 hours ago
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...
smt88 | 19 hours ago
First, modern vanilla JS APIs have been available for more than ten years. A browser without them is absolutely ancient.
And for the browsers that are truly that old, you can use nearly-weightless polyfills instead of jQuery.
olmo23 | 4 hours ago
hot take: we should not be supporting them.
(i get that this is a hard sell if you use your website to make money)
xp84 | 20 hours ago
saidinesh5 | 20 hours ago
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.
treve | 16 hours ago
smt88 | 19 hours ago
proxyscore | 18 hours ago
nchmy | 7 hours ago
carlosjobim | 2 hours ago
chuckadams | 21 hours ago
abanana | 20 hours ago
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.
nixpulvis | 20 hours ago
recursive | 20 hours ago
chuckadams | 20 hours ago
recursive | 19 hours ago
You'd probably usually chain that inside the callback. Instead of addClass('foo').hide(), you'd do el.classList.add('foo'); el.hidden = true; or something. It's not 1:1, but also it's not really that big a deal.
wvbdmp | 20 hours ago
skrtskrt | 15 hours ago
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.
benatkin | 13 hours ago
nchmy | 7 hours ago
nchmy | 7 hours ago
bpiroman | 21 hours ago
grugdev42 | 7 hours ago
Kuyawa | 21 hours ago
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
rico735 | 19 hours ago
theandrewbailey | 6 hours ago
So is AI.
dmix | 21 hours ago
vrubleg | 21 hours ago
umvi | 20 hours ago
joel2oliver | 20 hours ago
alehlopeh | 20 hours ago
xp84 | 20 hours ago
sigzero | 20 hours ago
joel2oliver | 16 hours ago
blinkbat | 20 hours ago
thrownaway561 | 20 hours ago
dday9 | 19 hours ago
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!
scottchiefbaker | 19 hours ago
dday9 | 3 hours ago
I wasn't talking about version 4.1, this would have been version 1.x (maybe 1.5... it was ~15 years ago), and the issue was bandwidth usage for uber remote users. There were all sorts of tricks I remember implementing to get that project over the finish line, but one of them was definitely yoinking jQuery out of the project, despite me being a big advocate for the library.
dwoldrich | 18 hours ago
The modern fetch API is better though because it's a Promises API and it can stream as raw bytes, not characters:
bastawhiz | 17 hours ago
RunSet | 3 hours ago
https://bugzilla.mozilla.org/show_bug.cgi?id=505521
dday9 | 3 hours ago
tkslucas | 19 hours ago
pluc | 19 hours ago
Velocifyer | 18 hours ago
bastawhiz | 18 hours ago
bastawhiz | 18 hours ago
Prathamdeshmukh | 17 hours ago
Did not know this library is still being maintained
noduerme | 15 hours ago
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.
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.
devsda | 14 hours ago
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.
Just open the firebug console, and try the examples for selectors, callbacks etc.
dday9 | 3 hours ago
goertzen | 5 hours ago
* brief snapshots on what’s interesting, valuable and good about some random thing
thx for sharing and taking the time to write it noduerme
zhisme | 12 hours ago
faramarz | 12 hours ago
grugdev42 | 7 hours ago
jszymborski | 2 hours ago