jQuery

“Jquery hit its limits supporting that reasonably, sometime around the early 2010s.”

“Now that IE is dead and most of the cross-platform implementation differences have been fixed”

“Browser inconsistencies in the early days were practically insurmountable without jQuery to provide a consistent API surface.”

“so much of it was a nightmare that just got endless workarounds heaped on top for basic performance issues”

“IMO it is literally not possible for a medium+ jQuery app to fit in a brain or be maintained easily”

“I prefer the terseness of jQuery's API and things like chaining dom operations with the fluent API”

“JQuery serves very well for that and for keeping me out of browser compatibility issues”

“Too many unpredictable side effects. Changing one thing breaks something else.”

“prefer older boring solutions like surgical jquery or htmx-style islands of interactivity”

“I'd take JQuery's dom manipulations and standard-library improvements over the native apis”

“the vast majority of its once handy features are now baked into JS in the browser by default”

“If I'm building something for myself it's always Django + HTML/jQuery”

“Server side rendering + htmlf endpoints and JQuery load was always the sweet spot for me”

“hasn't fundamentally changed since I was a wee lad doing web dev”

“It's fantastic up until that point, and incredibly easy to footgun beyond it.”

“jQuery, for as long as it's been around has had very few major releases, 4 now.. and very few breaking changes... hardly "biting"”

“The clean and simple syntax was always the reason to use jQuery”

“after JQuery 1.x, and in particular, the changing, the deprecating, and the dropping of things here and there, JQuery no longer made sense”

“I don't think there's a reason to go out of your way to use it just for the sake of using it.”

“quickly exceeded my goal of keeping the front-end at under 40KB total gzipped”

“how wonderful it was to work with in the age of browser inconstancies”

“jQuery made development possible without debugging across three browser varients.”

“Theres so many things I built on top of jQuery in those early years that likely still work.”

“Breaking changes means more of an upgrade hassle on something that's already not worth much of an upgrade hassle to begin with.”

“I love jQuery and it’s elegant methods chaining over object / array of DOM elements you keep in the chain.”

“sometimes a judicious use of old familiar tool gets the job done”

“The terse and chainable jQuery syntax is more readable, easier to remember, and thus more pleasant to maintain.”

“being imperative, it quickly becomes complex when you need to handle more than one thing”

“Safari from iOS 16, released in 2022, is more modern in every conceivable way than MSIE 11.”

“Breaking backwards compatibility to turn 27kb into less because of "bloat" makes less sense to me.”

“I cannot express how much I admire the amount of effort jQuery puts into their upgrade tools.”

“jQuery is still my way to go for any website requiring some custom interaction that isn't available in vanilla js.”

“jQuery does a lot more though, and includes support older browsers.”

“It's nice that jQuery still supports those users and the products that they are still running.”

“$() CSS parsing and DOM traversal was way slower than querySelector or getElementById”

“it's like 30k minimised and just bridged a bunch of functionality that browsers lacked at the time”

“takes a very global approach to the DOM, which will naturally lead to spaghetti code”

“It can get unwieldy compared to keeping all your rending logic in one place and applying data to it like in React.”

“raw JavaScript with some basic utilities like jQuery is not so bad”

“The best outcome was things like jquery and then lodash where a whole collection of small util functions get rolled in to one package.”