Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

jQuery 4

blog.jquery.com

Post reply on HN
Print view View original

81–90 of 313 posts

Re: jQuery 4

#81

Post by kstrauser »

sebazzz wrote: post #67
kstrauser wrote: post #55

Earlier quoted context omitted.

This is the part that I find the strangest: > We also dropped support for other very old browsers, including Edge Legacy, iOS versions earlier than the last 3, Firefox versions earlier than the last 2 (aside from Firefox ESR), and Android Browser. Safari from iOS 16, released in 2022, is more modern in every conceivable way than MSIE 11. I'd also bet there are more people stuck with iOS 16- than those who can only us…

“Support” here probably means “we’re testing jQuery for compatibility on those web browsers” - likely Safari from iOS 16 still runs this version of jQuery just fine. However, running automated test suites or support bugfixing for those clients is a lot harder than spinning up some Microsoft-provided VM with IE11 on it.

Fair point.

Re: jQuery 4

#82

Post by KellyCriterion »

hypnot wrote: post #78

It's amazing how much jQuery is still used today. Even on modern websites you can often find it included (browser devtools -> jQuery in the console, and see). And not just on hobbyist sites, but on serious company websites and their web tools as well.

Curious:

Whats the current behemoth instead of JQ?

I perceive it as still being the de-facto standard?

Re: jQuery 4

#83

Post by downsplat »

topspin wrote: post #58
maxloh wrote: post #5

Even after migrating to ES modules, jQuery is still somewhat bloated. It is 27 kB (minified + gzipped) [0]. In comparison, Preact is only 4.7 kB [1]. [0]: https://bundlephobia.com/package/jquery@4.0.0 [1]: https://bundlephobia.com/package/preact@10.28.2

> Preact is only 4.7 kB Is there some outlier place where people using virtual DOM frameworks don't also include 100-200kb of "ecosystem" in addition to the framework? I suppose anything is possible, but I've never actually seen it. I have seen jQuery only sites. You get a lot for ~27kB.

I do that when I need to make a simple SPA. Plain Vue plus a few tiny add-ons of my own.

Re: jQuery 4

#84

Post by altern8 »

b3ing wrote: post #3

Nice to see it still around and updated. The sad part is I guess this means React will be around in 2060.

What's wrong with React?

It made it so much better to build apps vs. spaghetti jQuery.

I still have nightmares about jeeping track of jQuery callbacks

Re: jQuery 4

#85

Post by [deleted] »

lioeters wrote: post #76
blakewatson wrote: post #20

Related: This is a nice write-up of how to write reactive jQuery. It's presented as an alternative to jQuery spaghetti code, in the context of being in a legacy codebase where you might not have access to newer frameworks. https://css-tricks.com/reactive-jquery-for-spaghetti-fied-le...

This brought me flashbacks of jQuery spaghetti monsters from years ago, some were Backbone related. In retrospect, over-engineered React code can be worse than decently organized jQuery code, but some jQuery mess was worse than any React code. So I guess I'm saying, React did raise the bar and standard of quality - but it can get to be too much, sometimes a judicious use of old familiar tool gets the job done.

[deleted]

Re: jQuery 4

#87

Post by Strom »

troupo wrote: post #75
kstrauser wrote: post #55

Earlier quoted context omitted.

This is the part that I find the strangest: > We also dropped support for other very old browsers, including Edge Legacy, iOS versions earlier than the last 3, Firefox versions earlier than the last 2 (aside from Firefox ESR), and Android Browser. Safari from iOS 16, released in 2022, is more modern in every conceivable way than MSIE 11. I'd also bet there are more people stuck with iOS 16- than those who can only us…

> Safari from iOS 16, released in 2022, is more modern in every conceivable way than MSIE 11. There are likely millions if not tens of millions of computers still running MSIE11. There are likely to be no devices running iOS 16

> There are likely to be no devices running iOS 16

My iPhone X is stuck on iOS 16 with no way to upgrade.

However, the phone is still working well. Despite being in daily use for 8 years it still has 81% battery capacity, has never been dropped, has a great OLED screen, can record 4K@60 video. It is far more responsive than a brand new 2025 $200 Android phone from e.g. Xiaomi. It still gets security patches from Apple. The only real shortcoming compared to a modern iPhone is the low light camera performance. That and some app developers don't support iOS 16 anymore, so e.g. I can't use the ChatGPT app and have to use it via the browser, but the Gemini app works fine.

Re: jQuery 4

#88

Post by troupo »

kstrauser wrote: post #80
troupo wrote: post #75

Earlier quoted context omitted.

> Safari from iOS 16, released in 2022, is more modern in every conceivable way than MSIE 11. There are likely millions if not tens of millions of computers still running MSIE11. There are likely to be no devices running iOS 16

According to Cloudflare, there are almost no users still on MSIE of any version.[0] Statcounter says there are about 4.6% of iOS users still on iOS 16.[1] My gut instinct is that there are multiple times more people using iOS 16 today than MSIE of any version. [0] https://radar.cloudflare.com/reports/browser-market-share-20... [1] https://gs.statcounter.com/os-version-market-share/ios/mobil...

IIRC public counters tend to miss corporate networks.

Re: jQuery 4

#89

Post by sgt »

flomo wrote: post #51

Whenever HTMX comes up here, I always think "isn't that just some gobbledy-gook which replaces about 3 lines of imperative jquery?" Anyway, jQuery always did the job, use it forever if it solves your problems.

I pretty much use HTMX and vanilla JS to solve most problems, when I use Django at least. Keeps things simple and gives that SPA feel to the app too.

Re: jQuery 4

#90

Post by egeozcan »

doix wrote: post #23
Klaster_1 wrote: post #21

Earlier quoted context omitted.

I used this approach before and it indeed works better than the 2010-style jQuery mess. A good fit for userscripts too, where the problem you attempt to solve is fairly limited and having dependencies, especially with a build steps, is a pain. Note that you don't need jQuery for this at all, unless you are somehow stuck with ancient browser support as a requirement - querySelector, addEventListener, innerHtml - the b…

Unfortunately, nowadays writing userscripts is much harder than it used to be. Most websites are using some sort of reactive FE framework so you need to make extensive use of mutationObservers (or whatever the equivalent is in jQuery I guess).

It's easier to write with LLMs. One-off projects (the way I treat userscripts) is where they really shine.

Oh the horrible things I do with Instagram...

Post reply on HN