Hacker News Reader

Comment by forthefuture | Hacker News Reader

If anything it feels like io.js might make it out alive if Node turns into something akin to jQuery.

Could you clarify this? Have we stopped using jQuery? Actually I find myself switching back and forth between io and node with little trouble. If that becomes untenable, one might have to make choices, but we're not there yet.

Mostly in regards to pace of progress. Whenever the bureaucracy is smaller you can get more done faster. jQuery is just a good example of something that has become relatively bloated with time, with almost no real hope of ever improving to the point that it's not one of the first things you micro optimize out of your libraries.

Of course jQuery is bloated, but of course jQuery would be bloated by this time. The only way to have avoided that would have been to split out the compatibility layer and let people just load whatever portion of it they want. Then you'd have people complaining that when they load enough to support ie8 it seems bloated. b^) Also that architecture probably would have been an ongoing annoyance for jQuery maintenance. (EDIT: yes I know about v2, I'm just saying that what jQuery would become was pretty much decided, architecturally, long before that release.)

It isn't clear that node had to go that direction, or even that they can't change course now.

http://jquery.com/browser-support/

jQuery 2.x dropped support for <= IE8.

Can you explain the comparison to jQuery? I wasn't aware that jQuery was dead.

It's not dead, people have just taken to talking about Angular and React more.

While all the new stuff has value, to me the value of frameworks will always lie in prototypes and small projects, with big production projects needing the flexibility of libraries.

I don't think jQuery will be going anywhere until the DOM itself evolves past a need for it or we evolve past a need for the DOM

Reply on news.ycombinator.com