Live data from Hacker News

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

blog.jquery.com

111–120 of 237 posts

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

#111
post #77

Earlier quoted context omitted.

> IE7 is a bit too soon, but IE8?... It was released in 2009! That's old! When JQuery 1.9 is released in 2013 it'll be four years old. Windows XP is eleven years old and will be end of lifed in early 2014. At what point will you pull the pin? I think this is a good roadmap for phasing out Old IE support. It's not like they're yanking the rug out from under you - 1.9.x will be around for a while yet.

You realize IE8 is the default browser that shipped with Windows 7, right?

What, nobody uses Windows update?

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

#112
post #101
post #92

Earlier quoted context omitted.

That's so much BS. Like supporting old browsers is that hard/expensive. Everyone keeps saying that, but I have never ever seen numbers to back it up. Letting it all blow up in the user's face is not an option to me. And I do business with publicity agencies, they don't give a fuck about this stuff, as far as they know everyone owns the latest macbook.

I'll tell you the numbers. We spend way too much effort trying to make our sophisticated web app work with ie7. The industry demands innovation in ux but it's nearly impossible to provide it when you are writing for 4 browsers. In a lot of cases we struggle for hours on one problem and end up writing a separate implementation for that feature that doesn't perform as well. Now we have segmentation in experience, help…

FYI: you didn't mention any numbers like you promised.

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

#113
post #32

So if the market share report links below are in the ballpark, that is about 60% of IE's current 49% market share, or about 29% of all current browsers. This makes jquery 2 a non-starter. Even using 1.9 is suspect because the questionable decision making process here makes me think I will have more headaches in the future if I stick with jQuery. IE Market Share: http://bit.ly/LUhxlA IE Version Market Share: http://bi…

Interesting way of looking at it. Except that is about 70% of browsers that will work with jquery 2.0. Puts it into perspective!

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

#114
post #96

Earlier quoted context omitted.

Which other libraries would those be? (I'm serious.) There were several fairly well known libraries a couple of years ago, but as far as I can tell, jQuery won that battle decisively. It has almost 100% penetration in the projects I'm familiar with that use a general purpose JS library, and it seems to be the default for articles and blog posts I find on-line these days too. Part of that success came from the ecosyst…

What do you mean by "comprehensive enough"? Can't you read the code?

I mean in terms of functionality.

To be worth shifting away from the jQuery ecosystem to something new, the latter needs a compelling advantage and it needs to not have any deal-breaking disadvantages. Nothing I've come across so far myself seems to meet both criteria.

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

#115
post #92

Earlier quoted context omitted.

That's so much BS. Like supporting old browsers is that hard/expensive. Everyone keeps saying that, but I have never ever seen numbers to back it up. Letting it all blow up in the user's face is not an option to me. And I do business with publicity agencies, they don't give a fuck about this stuff, as far as they know everyone owns the latest macbook.

No, it's not difficult to support oldIE. Single Column, nothing fancy. But the business people don't want that. They want it to look identical in every browser, and the web designers are scared shitless of losing money to tell them different. The problem is that business people don't know that hours of extra work are required to do this. And when they are told they don't care.

There is a simple solution for that, add it to your bill / launch estimates. Every client I have had always understands when you say "It'll cost X to support that, or it'll bump your launch date 2 weeks". They may not understand the technical details but they will understand when you put it in their terms and ask them "Worth it to you or not?"

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

#117
post #57

Earlier quoted context omitted.

>JQuery has just set a time limit on proper web access for an entire OS. doesnt chrome work on xp?

Every browser vendor still supports Windows XP. The only exception is Microsoft. IE9 only works on Vista and Win7. IE10 will only work on Win7 and Win8.

So if everyone is flipping shit about how outrageous it is to not support IE7/8... why do we let Microsoft slide on not supporting their own damned product?

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

#119

You will not only be stuck with 1.9, but every other library you use that is based on jQuery - and most in my stack are - can't be upgraded as I assume those libraries will not play conservative but switch to 2.0 (and 2.1 next)

1.9 and 2.0 have the same api

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

#120

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 was never good at this. When I first used it on a project they had already drooped support for Safari 1.x, despite that being available version of Safari available for Mac OS X 10.4.

I was, at the time, living with my girlfriend and a friend of hers, both of whom used 10.4 and Safari 1.x: it was honestly quite common among people who couldn't quite afford new computers.

Regardless, when we sent the demo of our product for the local school district I was getting reports that the entire browser was crashing, which I traced down to some sketchy code in jQuery that had been tested so poorly on this version of Safari that no one noticed this highly fatal error.

When I reported the issue to a major jQuery contributor (a friend of mine), all I got was flak that people shouldn't be using that browser and should upgrade to 10.5... obviously I have never used jQuery in a project again.

Post reply on HN