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

201–210 of 313 posts

Re: jQuery 4

#201

Post by gloryjulio »

Capricorn2481 wrote: post #194
normie3000 wrote: post #187

Earlier quoted context omitted.

> I kid you not, there were 30+ redux actions chaining in the most incomprehensible ways I 100% believe this, as it describes all the redux codebases I've seen. The library seems to be an antipattern of indirection.

I really can't understand how someone would make 30 redux actions for a simple use case, as someone has implemented the exact same thing. But yes, not a fan of Redux myself

Many years ago, I used Redux to build real time streaming data processing layer. Basically I need to receive, merge, and process multiple data streams into a single realtime data pool. After that,consuming the realtime data becomes dead easy.

Even now I am not sure I could find a better tool to deal with real time data and synchronization. But for simple crud Redux is mostly overkill

Re: jQuery 4

#202

Post by loglog »

Capricorn2481 wrote: post #194
normie3000 wrote: post #187

Earlier quoted context omitted.

> I kid you not, there were 30+ redux actions chaining in the most incomprehensible ways I 100% believe this, as it describes all the redux codebases I've seen. The library seems to be an antipattern of indirection.

I really can't understand how someone would make 30 redux actions for a simple use case, as someone has implemented the exact same thing. But yes, not a fan of Redux myself

Have some pity for those Senior Expert Architect Full-Stack Developers (fresh out of boot camp) in urgent need of job security.

Re: jQuery 4

#203

Post by sodafountan »

Wow, this is interesting to see. I thought jQuery was dead.

My next question would be, is this something that OpenAI and Anthropic would train their data on? If I ask Claude Code to write an app and utilize jQuery, would it resolve to the previous version until it's retrained in a newer model?

Re: jQuery 4

#204

Post by giancarlostoro »

Much like I am sure anyone else who started doing web dev in the 2000s and 2010s before SPA frameworks were as prevalent I learned web development scripting with jQuery and I am happy to see its still around. Theres so many things I built on top of jQuery in those early years that likely still work. Kudos to the team.

Re: jQuery 4

#206

Post by alnico »

vanderZwan wrote: post #195
alnico wrote: post #184

Congrats to everyone involved in the jQuery 4.0 release. For what it’s worth, if you’re looking for a more structured approach on top of jQuery, JsViews ( https://jsviews.com ) provides a reactive templating and data-binding system that’s been around and stable for many years. It hasn’t seen the same level of adoption as newer frameworks, but it may still be of interest to people who prefer the jQuery ecosystem.

That looks interesting, I'm not likely to write any jQuery any time soon, but I'll check out the source code to see if I can learn anything from it. Regarding adoption levels, the JsViews website made me think I had accidentally toggled the "Desktop Site" option in my Iceweasel browser, I wonder if that scared people off. Or perhaps it's because, as others mentioned, most jQuery development these days is in legacy co…

I’ve been collaborating with Boris, the author of JsViews, and we do have plans to modernize the website—which speaks directly to your point about first impressions and adoption. You’re absolutely right that presentation matters; if something looks dated, people may disengage before digging any deeper.

I also raised the jQuery dependency concern with Boris for exactly the reason you mentioned: many teams automatically rule out anything that requires jQuery, especially outside of legacy codebases. That’s a real barrier today.

For what it’s worth, a jQuery-free version may happen. Boris is actively exploring it, but he’s making no promises—it’s a non-trivial problem and would effectively require a full rewrite rather than a simple refactor.

Re: jQuery 4

#207

Post by wqweto »

pmontra wrote: post #109
kstrauser wrote: post #80

Earlier quoted context omitted.

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

I visited a distillery in 2020. Their machines were managed by HP laptops running Windows XP. Those machines and those laptops and that Windows XP are probably still there with their old IE browser.

XP support IE8 max

Re: jQuery 4

#208

Post by wqweto »

simondotau wrote: post #68
jbullock35 wrote: post #8

Earlier quoted context omitted.

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

Surely by this point someone has written a 0-day for MSIE 11 which gets root and silently installs an Internet Explorer skinned Chromium. If not, someone should get onto that. —Signed, everyone

Last available Chromium on XP has 0-days too, so not a big win.

Re: jQuery 4

#209

Post by rolymath »

recursivedoubts wrote: post #192
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.

yes: htmx grew out of intercooler.js, which was based on jquery and inspired by the jQuery.load() method: https://api.jquery.com/load/ which I found while doing some performance work at one point. intercooler.js started as a custom function that hooked .load() in based on custom attributes (a trick I learned from angular 1.x) deeply respect and love jquery

Are you Carson?

Re: jQuery 4

#210

Post by recursive »

Zardoz84 wrote: post #174
hsbauauvhabzb wrote: post #73

Earlier quoted context omitted.

These days I’ve moved to native JS, but hot damn the $() selector interface was elegant and minimal vs document.getElement[s]by[attribute)]. While presumably jquery is slower than native selectors, maybe that could be pre-computed away.

const $ = document.querySelectorAll

Probably have to bind the this value.
Post reply on HN