Live data from Hacker News

JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

blog.jquery.com

11–20 of 237 posts

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#11
I love this product roadmap write up!

Explanations littered with reasoning and also a code-level solution for something that won't be an issue until one year down the road. Hopefully that 93KB (un-Gzipped) beast can be knocked down a bit with 2.X.

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#12
post #10
post #5

Isn't one of the reasons for jquery to "abstract away" the differences between browsers so I don't have to worry about it? Dropping support for popular browsers doesn't seem to help me much.

It does seem a strange decision. They even address it in their post: "jQuery was conceived specifically to address the differences in browsers, so we’re not going to abandon the essence of our philosophy and simply disregard the millions [still using] oldIE. Yet we also want to move ahead and take advantage of modern browsers, especially the growing mobile market." The whole point of jQuery is that it's supposed to a…

I think they just realized they can continue to support the old IE versions while other JS libraries advance in functionality, or they can stay competitive.

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#13
post #9

Earlier quoted context omitted.

Not sure if you read the article, but 1.9 and 2.0 will basically be the same, just different underlying code. 1.9 will support IE<9, and 2.0 will be smaller/faster/more stable

Ok. So, if I upgrade and someone does visit from an older IE browser what happens? :) I'll be back to testing browser differences. I guess those are pretty old browsers, so oh well.

well they do provide 1.9 to handle that, this is is how they recommend you handle that

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#15
post #9

Earlier quoted context omitted.

Not sure if you read the article, but 1.9 and 2.0 will basically be the same, just different underlying code. 1.9 will support IE<9, and 2.0 will be smaller/faster/more stable

Ok. So, if I upgrade and someone does visit from an older IE browser what happens? :) I'll be back to testing browser differences. I guess those are pretty old browsers, so oh well.

It's pretty simple– if you want to support IE<9, don't upgrade to jQuery 2.x. A lot of people are already dropping support for IE<8.

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#17
post #14

Zepto is already a popular option for those who want jQuery features in a lightweight library. The API is essentially identical to jQuery, making it a drop-in replacement at a fraction of the size. zeptojs.com

Zepto is not drop in. Not even close.

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#18
Sorry, but this is a disaster. Dropping support for IE6 may be OK, IE7 is a bit too soon, but IE8?

I haven't tested my stuff on IE6 and IE7 for a long time, but I still do it on IE8 everyday. It was released in 2009! And it's decent enough, PNG transparencies, etc.

jQuery's main raison d'être might have gone out the window.

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#19

Sorry, but this is a disaster. Dropping support for IE6 may be OK, IE7 is a bit too soon, but IE8? I haven't tested my stuff on IE6 and IE7 for a long time, but I still do it on IE8 everyday. It was released in 2009! And it's decent enough, PNG transparencies, etc. jQuery's main raison d'être might have gone out the window.

"jQuery's main raison d'être might have gone out the window." - my thoughts, exactly!

Re: JQuery 2.0 Drops Support for IE6/7/8; API-Compatible with jQuery 1.9.

#20

Sorry, but this is a disaster. Dropping support for IE6 may be OK, IE7 is a bit too soon, but IE8? I haven't tested my stuff on IE6 and IE7 for a long time, but I still do it on IE8 everyday. It was released in 2009! And it's decent enough, PNG transparencies, etc. jQuery's main raison d'être might have gone out the window.

The premise is that jQuery 1.9 and 2.0 are API-compatible, so you can do something like:

    
        
    
    
        
    
New browsers will get a lighter download and a faster runtime. oldIE will still work with all the hacks required to make it work.
Post reply on HN