today at 12:45 AM
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.
yesterday at 8:32 PM
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.
yesterday at 9:06 PM
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.
For those unfamiliar, I recommend looking at https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast... and searching for the 201 instances of
: this
in that file. A remarkably fluent API. We could all be so elegant.today at 12:03 AM
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.
today at 12:03 AM
Mootools was way better but never got the attention jquery got.
yesterday at 11:23 PM
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).
I hope https://github.com/tc39/proposal-pipeline-operator and perhaps also https://github.com/tc39/proposal-do-expressions will put it to rest.
yesterday at 9:39 PM
This is called a fluent interface. [1] C++ streams are perhaps the most common example of this pattern.
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
yesterday at 10:14 PM
Fluent interface is method chaining, and it's already obviously in JS. The proposed pipeline operator is neither method chaining nor fluent interface.
yesterday at 10:37 PM
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.
yesterday at 11:20 PM
What is the "whole idea" of a fluent interface if not specifically method chaining?
yesterday at 11:33 PM
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.
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.
today at 1:20 AM
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.
today at 12:18 AM
amen
yesterday at 8:54 PM
Are you talking about method chaining, something that comes from JavaScript (technically the DOM I suppose), not jQuery?
yesterday at 8:58 PM
Method chaining is library-specific, a function of methods returning `this`/`self`.
jQuery made the decision to do this, not JavaScript.
yesterday at 9:37 PM
Yes, I'm talking about using JS' method chaining. That's what I mean by "going with a language's features".
yesterday at 8:57 PM
It was not commonplace at the time jQuery was released.
yesterday at 9:03 PM
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.
yesterday at 9:30 PM
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.
yesterday at 10:25 PM
> 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.
yesterday at 10:30 PM
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.
yesterday at 10:25 PM
That's a lot of stuff just for [...nodeList].
yesterday at 10:36 PM
jQuery predates that syntax, but have fun chaining that even now.
yesterday at 11:45 PM
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.
yesterday at 10:33 PM
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.
yesterday at 9:12 PM
There is a heap of indie devs that swear by jQuery and avoid the frameworks like react. Each has their use cases.
yesterday at 9:27 PM
What’s a use case for jQuery over vanilla JS?
When most code is and will be written by AI, why would I sacrifice performance for syntactic sugar?
yesterday at 10:11 PM
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.
yesterday at 10:20 PM
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.
yesterday at 11:02 PM
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.
today at 12:10 AM
Yes and reading resigs book on how he made jquery, well I can't say anything but the guy was a genius way ahead of it's time.
yesterday at 10:04 PM
Vanilla JS only works with a recent browser. JQuery works with old garbage people never updated.
yesterday at 11:01 PM
This is absolutely not a reason to use jQuery. This reason is 15+ years old.
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.
yesterday at 10:22 PM
But what old garbage browsers are still in use?
yesterday at 10:33 PM
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.
yesterday at 11:01 PM
Why use jQuery instead of situational, atomic polyfills that just provide the functionality you’re actually using?
yesterday at 11:28 PM
Single download is better than multiple small downloads.
today at 12:59 AM
Is "modern" jQuery tree-shakeable? If not, individual polyfills will be way smaller.
yesterday at 11:41 PM
Ain't no law saying that you can't bundle multiple polyfills.
yesterday at 11:47 PM
You can. And that's how you get jQuery
yesterday at 10:34 PM
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.
1: https://blog.jquery.com/2026/11/17/jquery-4-1-0-and-3-8-0-re...
yesterday at 9:56 PM
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.
yesterday at 9:58 PM
I wouldn't say there are _many_ use cases, but "LLM is writing code in a legacy codebase without heavy refactors" fits your question.
yesterday at 10:02 PM
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.
yesterday at 10:58 PM
Why would AI have a harder time with vanilla JS?
yesterday at 9:08 PM
I would probably use Hyperscript for that use case: https://hyperscript.org/
yesterday at 11:08 PM
Good luck getting your boss to commit that $40 million project to a meme language.
yesterday at 9:08 PM
I wonder how many websites on the web still use jquery today
yesterday at 10:16 PM
StackOverflow still does. Delivered via Google for no good reason other than to give them tracking data on SO users.
yesterday at 11:29 PM
A lot actually
yesterday at 10:24 PM
If you believe a google query:
Approximately 64% of all websites—or roughly 67 million live domains—currently use jQuery.
yesterday at 9:12 PM
>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.
yesterday at 10:14 PM
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.
yesterday at 10:31 PM
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.
yesterday at 9:26 PM
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.
yesterday at 10:01 PM
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!
yesterday at 10:14 PM
Netscape was not the same era as jQuery.
yesterday at 10:19 PM
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.
yesterday at 10:26 PM
I don't think he was equating the two. Just saying how bad it was to deal with them. I could be wrong.
yesterday at 8:02 PM
I'm actually surprised (in a good way) that it's still maintained, and it still helps half of the internet to function
yesterday at 11:02 PM
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!
today at 12:15 AM
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:
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();
-------------------The modern fetch API is better though because it's a Promises API and it can stream as raw bytes, not characters:
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");
}today at 12:52 AM
It's actually a little easier these days:
const response = await fetch("/stream");
for await (const value of response.body) {
console.log("Received", value.length, "bytes");
}
console.log("Finished")yesterday at 11:16 PM
[dead]
yesterday at 9:35 PM
One of the nice things about LLMs is you can port 10+ year old apps using jQuery to vanilla js pretty easily.
yesterday at 11:14 PM
today at 12:21 AM
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.
today at 12:49 AM
Does it actually not work on browsers from two years ago?
yesterday at 8:06 PM
I wonder if people use jQuery on their new projects. Vanilla JS has come a long way since jQuery was king.
yesterday at 8:09 PM
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.
yesterday at 10:20 PM
> 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.
today at 12:51 AM
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
yesterday at 8:33 PM
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...
yesterday at 9:25 PM
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.
yesterday at 10:07 PM
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.
yesterday at 10:51 PM
> permanently disabled
Only on Windows 10 and 11. It still runs as it always did on previous Windowses.
yesterday at 8:36 PM
It is still less verbose than the DOM navigation APIs that landed on the browsers.
yesterday at 8:13 PM
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.
yesterday at 9:04 PM
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.
yesterday at 10:24 PM
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.
yesterday at 9:53 PM
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.
yesterday at 8:15 PM
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.
yesterday at 8:37 PM
Add your own `.notEmpty()` custom plugin / $.fn method to throw that exception. The rest of the world can stay as-is.
yesterday at 11:25 PM
Legendary drop, so many great memories
yesterday at 8:39 PM
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.
yesterday at 8:43 PM
would you define "complex ui" and what tools you would recommend "today" as an alternative to BS/JQ.
yesterday at 9:04 PM
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.
yesterday at 9:44 PM
[dead]
yesterday at 9:38 PM
replace jquery with
$ = (q) => document.querySelector(q)
and $$ = (q) => document.querySelectorAll(q)
and you're good to goyesterday at 9:48 PM
No, you're not.
jQuery returned useful collections. DOM methods return an anemic NodeList which doesn't even implement Array interface.
yesterday at 10:09 PM
That's why I do
$ = (selector) => Array.from(document.querySelectorAll(selector))
Still not as good as the original, but somewhat usable at least :/yesterday at 10:21 PM
There are small libraries like umbrellajs that just provide a jquery-like DOM interface if that's all you want.
yesterday at 9:51 PM
$('body').childNodes.forEach(console.log)
I see a beautiful collection thereyesterday at 9:54 PM
NodeList exposes exactly 5 methods: item, entries, forEach, keys, and values.
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.
yesterday at 10:27 PM
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.
yesterday at 8:36 PM
I was about to say, but datatables.net! But version 3, as of July 2026, has dropped the jQuery dependency.
https://datatables.net/blog/2026/datatables-3
yesterday at 8:03 PM
In the age of AIs and Reacts, people would never realize the pleasure and the ease jQuery provided with shitty browsers like IE6!
yesterday at 8:06 PM
Also just much better JS builtins. document.queryselector and map/filter were many, many years away.
yesterday at 8:43 PM
The selector syntax is still more readable and less verbose in jquery too, IMO
yesterday at 8:53 PM
It's the same syntax tho? jQuery uses CSS selectors (with a few extensions), querySelector uses CSS selectors.
yesterday at 8:01 PM
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.
yesterday at 8:04 PM
Both Prototype JS and MooTools!
yesterday at 9:38 PM
add script.aculo.us to the list as well!
yesterday at 9:37 PM
[dead]
yesterday at 8:43 PM
I came here to reminisce about MooTools, the discerning dev’s jQuery ;)
yesterday at 9:37 PM
It's a 2026 release, and jQuery still didn't drop 13-years-old IE11 :) https://github.com/jquery/jquery/pull/5077
yesterday at 11:34 PM
The little library that took on $.
yesterday at 8:57 PM
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.
yesterday at 9:01 PM
> It was disgusting and it ran in IE7.
So often was the case that the two ran together, especially with IE6.
yesterday at 9:31 PM
I'm tempted to go back to writing jQuery now!
yesterday at 8:12 PM
have you ever seen an ai suggest jQuery?
yesterday at 8:19 PM
my coworker's claude decided to write a bunch of perl the other day, so who knows?
yesterday at 8:32 PM
Ah yes, the ultimate vibecoding experience. Ask the AI to write your code in a write-only language.
yesterday at 8:34 PM
hah no, he was writing python, it decided to write perl on its own.
yesterday at 8:03 PM
Out of curiosity, are there still large projects using jQuery? Interesting that it is still maintained.
yesterday at 8:14 PM
Yes, about 63% of all websites: https://w3techs.com/technologies/details/js-jquery
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
yesterday at 8:33 PM
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
yesterday at 9:39 PM
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.
yesterday at 9:19 PM
Surely, I thought, cPanel/WHM no longer use jQuery, right? But it seems they might?? https://api.docs.cpanel.net/guides/guide-to-cpanel-interface...
yesterday at 10:09 PM
LFG
yesterday at 8:01 PM
Do they still build jquery ui? I kind of liked it and maybe will demand my agents start using it again for fun
yesterday at 8:06 PM
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.
yesterday at 8:11 PM
> I was there, Gandalf, I was there the day the strength of Men failed.
Unrelated, but it blew my mind when I learned that Elrond is half-man.
yesterday at 8:13 PM
I either somehow missed that, or forgot. So... today is the day I learned
yesterday at 9:39 PM
It's never said in the movies, they kind of imply he's like the king of elvens.
yesterday at 8:22 PM
I don't know if that was his Hitler dig or just a common trope, of people hating their own ancestry.
yesterday at 9:05 PM
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.
yesterday at 10:30 PM
Elrond never hated his ancestry.
today at 12:14 AM
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.
yesterday at 8:08 PM
Maintenance mode, but there have been some updates. Announcement: https://blog.jqueryui.com/2021/10/jquery-maintainers-update-...
yesterday at 8:35 PM
That was about "jQuery UI", a separate project.
yesterday at 8:49 PM
Yes. That's what this thread is about.
yesterday at 10:34 PM
This thread is about jQuery 4.1. jQuery UI is only up to 1.14
today at 12:25 AM
The post is about jQuery 4.1. The thread is about jQuery UI.
yesterday at 11:46 PM
kylee asked, "Do they still build jquery ui"
yesterday at 8:32 PM
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.
yesterday at 10:55 PM
[flagged]
yesterday at 9:34 PM
Some people hasn't awaken to the new AI dawn
You just don't need this. No jquery, no react, no tailwind, no fowntawesome, no external libs, no malware attack vectors, no waiting for a new update that never comes. It is all poison, just don't drink it and you'll be fine
yesterday at 11:35 PM
Sounds maintainable.
yesterday at 9:49 PM
[dead]
yesterday at 8:06 PM
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 :)