Live data from Hacker News

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

blog.jquery.com

91–100 of 237 posts

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

#91
post #34

Earlier quoted context omitted.

The cycle here is pretty long: jQuery 2.0 will be released in "Early 2013". For some time (probably at least 6 months if not longer), jQuery 1.9 and 2.x will be perfectly API compatible. That means that the conditional comment approach will work with very little downside. That gets us to summer or Fall 2013. At this point, there may be a release of jQuery 2.1. According to the blog post, it will probably contain few…

At the same time, the pace of the cutting edge grows faster and faster. It better grow pretty fast. By late 2012, jQuery will still be supporting a browser released in 2001 but by early 2013 it won't support a browser that was only replaced by MS in 2011. Corporate America is not IE8's only domain. There are a lot of people who don't even know what a browser is. And IE8 was the default browser on Windows 7.

I think it is MS's fault for taking years to speed up pace of browser development. DOM2 (important for jQuery) and XHTML are at least 10 years old now, and both are not supported by IE8 and took until IE9 to support.

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

#92
post #75

Earlier quoted context omitted.

That works fine for your blog, but what percentage of customers are you willing to turn away from your web business?

I the cost of maintaining apps exceeds their value as customers, then they're going to lose support. Don't forget supporting these old broweres isn't free, cheap, or easy.

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.

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

#93

Earlier quoted context omitted.

At the same time, the pace of the cutting edge grows faster and faster. It better grow pretty fast. By late 2012, jQuery will still be supporting a browser released in 2001 but by early 2013 it won't support a browser that was only replaced by MS in 2011. Corporate America is not IE8's only domain. There are a lot of people who don't even know what a browser is. And IE8 was the default browser on Windows 7.

You know what? At this point I'm not sure it's worth catering to people who "don't even know what a browser is." They've had nearly 20 years to hop on the bandwagon and start understanding this crazy "internet" thing, and they haven't. A person that behind the times isn't going to buy anything on the internet anyway.

>A person that behind the times isn't going to buy anything on the internet anyway.

Do you actually have some data to back that up? Because all the data I've seen says the exact opposite to what you are saying.

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

#94
I think this is a good move from jQuery. Other popular software/services should do it too, and it'll be THE END of awful IE versions.

I still do support IE8 but it is a pain in the ass to have to work around stupid bugs...pseudo elements are not well supported, font rendering is subpar, no css3 support, sloooow JavaScript engine...and I could go on for ever.

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

#95
post #7

Earlier quoted context omitted.

Fuck IE - they've done the same to us for years.

> Fuck IE - they've done the same to us for years. You're not "fucking IE" though, you're fucking the end-users; many of whom might be stuck on XP (and therefore IE8) without a huge choice. Corporate users, education users, those without the money to upgrade their OS/machine, etc.

Why are XP users stuck on IE8? (I mean I think there are a myriad of options that are pretty reasonable). It doesn't cost anything or fairly little labor to upgrade to a real browser over the course of a couple years. How far do we take this, why don't we all support IE5? It's time to let it go.

You can either stick with JQuery 1.9 for as long as you want to support IE8 (hopefully not more than 10 or 20 more years).

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

#96
post #12

Earlier quoted context omitted.

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.

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?

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

#97
To all the people upset about IE8 being the last browser supported on XP ... Isn't that Microsoft's problem rather than JQuery's? Apparently, Microsoft is not interested in providing a modern Web experience to their users.

I don't really see the problem anyway. JQuery can move forward, and those that want to support IE8 have JQuery 1.9 and I'm sure there will be a cottage industry of people maintaining updates to support IE8 for the next 20 or 30 years. In the meantime, the rest of the world will be able to move on. Perhaps people could even use UserAgents to provide legacy experiences for the IE8 crowd ... multiple views ... what a concept.

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

#98
post #20

Earlier quoted context omitted.

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.

We deal with enough conditionals already. Besides, sharing the same API won't stop you from bumping into some bug that's present in one version and not the other. We'll have to deal with two codebases. Download and runtime speed are not a problem on the Desktop. They should have had the guts to admit that this is all about mobile. Their denial at the end of the post is symptomatic.

Download and runtime speed are definitely a problem on desktop OSes -- mobile broadband, slow DSL, netbooks, that sort of thing.

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

#99
post #73

Earlier quoted context omitted.

You're comparing apples to oranges. A more correct assertion: By late 2012, jQuery will still be supporting a browser replaced by MS in 2006 but by early 2013 it won't support a browser that was only replaced by MS in 2011. It's still a valid point, but comparing release dates with replacement dates just hurts the whole argument.

You are right. Probably the best way would have been: By late 2012, jQuery will still be supporting a browser released in 2001 but by early 2013 it won't support a browser that was released in 2009.

jQuery 1.x supports all Microsoft browsers released over the past 11 years, while jQuery 2.x will only support Microsoft browsers released a little over a year before today.

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

#100
post #17

Earlier quoted context omitted.

Zepto is not drop in. Not even close.

Could you expand on that at all? I realise that Zepto covers a (very) small subset of jQuery functions, but I thought that in a lot of use cases it would be an appropriate substitute?

Last I checked zepto doesn't have support for any of the simulated selectors like `:checked`, `:input` and friends. If you use any of them, its not drop in.
Post reply on HN