Re:jQuery 4.1.0
by wouldbecouldbe on Tuesday November 17, 2026 @04:26PM
(#50538423)
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. So, $().ajax still handled its results with callbacks, it wasn't async, 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.
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.