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

41–50 of 313 posts

Re: jQuery 4

#46

Post by Klaster_1 »

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).

Very true. I guess that depends on what websites you find issues with? I just checked mine and all of those are quality of life improvements for fully server rendered sites like HN or phpBB forums.

Re: jQuery 4

#47

Post by flomo »

jbullock35 wrote: post #8
tartoran wrote: post #4

Earlier quoted context omitted.

Backwards compatibility. Apparently there are still some people stuck on IE11. It's nice that jQuery still supports those users and the products that they are still running.

Who is still stuck on IE 11---and why?

There are some really retrograde government and bigcorps, running ten year old infrastructure. And if that is your customer-base? You do it. Plus I worked on a consumer launch site for something you might remember, and we got the late requirement for IE7 support, because that's what the executives in Japan had. No customers cared, but yeah it worked in IE7.

Re: jQuery 4

#48

Post by mejutoco »

halapro wrote: post #38
onion2k wrote: post #9

Earlier quoted context omitted.

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

> includes support older browsers Which is entirely the issue. Supporting a browser for the 10 users who will update jQuery in 2025 is insane.

Breaking backwards compatibility to turn 27kb into less because of "bloat" makes less sense to me.
Post reply on HN