Live data from Hacker News

JQuery 2.0 Released

blog.jquery.com

21–30 of 226 posts

Re: JQuery 2.0 Released

#21
I was just debating the merits of going with one of the lightweight jquery substitutions for a phonegap app. This couldn't come at a better time.

Dropping the cruft and supporting 1.9 is such a wonderful way to go. Congratulations on a great release jquery team.

Re: JQuery 2.0 Released

#23
post #14

Serious question. Please hit me with a clue stick. Regarding 1.9, how can "old-IE compatibility often causes problems of its own" and "simplest way to support older browsers is to use jQuery 1.x on your site, since it works for all browsers." both be true at one and the same time?

This is one of the biggest projects on the web leading the way in throwing shitty old IE under the bus to help push the modern web forward. They're going to keep big-fixing 1.X so people stuck with IE6/7/8 can keep supporting it, but moving forward with 2.x for modern browsers makes their lives easier in the long run, and provides yet another coffin nail in Microsoft's attempt decade-old attempt to break the web.

Third parties have been trying to throw shitty old IE under the bus for a long, long time and haven't had much success in doing so. I fear jQuery 2.0 will see very low take-up on mainstream sites, and the resulting fork will be tricky to manage.

Re: JQuery 2.0 Released

#24

I think what a lot of people are upset about here, is jQuery entered the web development scene as "the library that solved cross-browser compatibility issues". Now while IE 6 is an obvious one to drop, IE 7 is a little tougher, and IE 8 is down right impossible to drop at this time. I understand that jQuery wants to promote a modern framework, but people didn't adopt it for it's fancy features. They adopted it becaus…

Sorry if I seem cranky, but did you READ the blog post? jQuery 1.9 supports those browsers and the jQuery team still supports it. Do you have a problem with us supporting a second version that can be smaller, faster, and work in places other than obsolete browsers?

It looks to me like he's worried (or saying that other people are/might be worried) about how long 1.9 will continue to be supported for.

Re: JQuery 2.0 Released

#25
post #8

Earlier quoted context omitted.

Keeping old-IE compatibility prevents some optimizations and makes the code have to do extra checks, but using one file that supports it is simpler than using two files?

Ok, so the problems it causes are pain points for the jQuery devs and not for website devs? Also, the underlying code is more complex and lacks optimizations? Until old drops off the radar completely we'll have to use 1.9 solely or do a conditional check and serve the suitable version - serving 1.9 seems simpler ^^, call me lazy, many have,

Its also a pain for every website serving jQuery because of increased data for every single page load. Cutting out the support for old IE should also help with performance.

Re: JQuery 2.0 Released

#26

Serious question. Please hit me with a clue stick. Regarding 1.9, how can "old-IE compatibility often causes problems of its own" and "simplest way to support older browsers is to use jQuery 1.x on your site, since it works for all browsers." both be true at one and the same time?

There's a difference between working as a web page in all browsers and working in all HTML-rendering environments such as the ones listed in the bullet points in the blog. For example, Windows 8 apps or Chrome add-ons have additional security restrictions on .innerHTML.

Re: JQuery 2.0 Released

#27

Serious question. Please hit me with a clue stick. Regarding 1.9, how can "old-IE compatibility often causes problems of its own" and "simplest way to support older browsers is to use jQuery 1.x on your site, since it works for all browsers." both be true at one and the same time?

[deleted]

Re: JQuery 2.0 Released

#28

I think what a lot of people are upset about here, is jQuery entered the web development scene as "the library that solved cross-browser compatibility issues". Now while IE 6 is an obvious one to drop, IE 7 is a little tougher, and IE 8 is down right impossible to drop at this time. I understand that jQuery wants to promote a modern framework, but people didn't adopt it for it's fancy features. They adopted it becaus…

Sorry if I seem cranky, but did you READ the blog post? jQuery 1.9 supports those browsers and the jQuery team still supports it. Do you have a problem with us supporting a second version that can be smaller, faster, and work in places other than obsolete browsers?

Did you consider an alternative to major version bumping, e.g. a slightly different name for this fork, such as jQuery-slim ... or a much better name? :-) I think the problem is that 2.0 just implies 'better' to such an extent that a lot of people will be concerned about 1.9's imminent sunsetting.

Re: JQuery 2.0 Released

#29
post #14

Serious question. Please hit me with a clue stick. Regarding 1.9, how can "old-IE compatibility often causes problems of its own" and "simplest way to support older browsers is to use jQuery 1.x on your site, since it works for all browsers." both be true at one and the same time?

This is one of the biggest projects on the web leading the way in throwing shitty old IE under the bus to help push the modern web forward. They're going to keep big-fixing 1.X so people stuck with IE6/7/8 can keep supporting it, but moving forward with 2.x for modern browsers makes their lives easier in the long run, and provides yet another coffin nail in Microsoft's attempt decade-old attempt to break the web.

They're not so much throwing IE under the bus as throwing developers under the bus that have fortune-500 clients that can only use IE. Some nerd (me) whining about their browser choice is really not going to make their IT director change policies.

Granted, I can and will keep using 1.9

Re: JQuery 2.0 Released

#30
post #9

Earlier quoted context omitted.

No, the idea has pretty much always been that jQuery 1.9 and 2.0 would be feature-comparable, just with different sizes and supported browsers. See http://blog.jquery.com/2012/06/28/jquery-core-version-1-9-an...

They hate IE SO much, they even made the drop a new major release. This is what I call commitment.

Since people see jQuery as a solution for cross-browser issues, dropping some browser support is the biggest change imaginable.
Post reply on HN