Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

blog.jquery.com

Post reply on HN
Print view View original

61–70 of 237 posts

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

#61

Post by ahoge »

elithrar wrote: post #33
mythz wrote: 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.

>stuck on XP (and therefore IE8)

Being stuck on XP does not mean that you have to use IE8. You can still use the latest version of Chrome, Firefox, Opera, or even Safari.

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

#62

Post by barryfandango »

tambourine_man wrote: post #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.

The app I work on dropped IE7 a year ago, and is dropping IE8 in January 2013. Therefore this is the opposite of a disaster, pretty timely actually.

They're pretty clear that 1.9 and 2.0 will have API compatibility so there is an option for those who still have to support oldIE and one for those who don't have to. Seems like the best possible arrangement.

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

#63

Post by anthonyb »

tambourine_man wrote: post #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.

> 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.

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

#64

Post by MatthewPhillips »

ahoge wrote: post #59
tambourine_man wrote: post #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.

>[IE8] was released in 2009! Yep, it's ancient. Chrome and Firefox are on average about 3 weeks old. IE8 is over 50 times older. >jQuery's main raison d'être might have gone out the window. Normalization was just one part. It still provides a much nicer API. There are also events, AJAX, effects, and some useful helpers. [].slice.call(document.querySelectorAll('p')).forEach(function (el) {console.log(el);}); vs $('p')…

Agreed, [].slice.call is show-offy and pointless. Array.prototype.slice.call is the way to go.

I hope you realize that by saving yourself a few characters you've sacrificed an unknown amount of performance from your site. For such a simple query I'd use getElementsByTagName instead.

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

#65

Post by barryfandango »

zanny wrote: post #53
jorgem wrote: 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.

Here is the magic: IE 6 - 8 are not popular browsers. They are only used if the person using them doesn't know what a browser is. And all it would take for them to switch is one webpage they use popping up "You are using an outdated unsupported vulnerable awful browser, here are Firefox or Chrome, take your pick and don't ruin your web experience any more". And the corporate clients could finally get through their he…

Unfortunately it's not a matter of sticking fingers in your ears, I can tell you. If you've got 50-100,000 workstations to worry about, and a couple of intranet apps that only run in older versions (there are more of these than you might think,) upgrading IE could be a fabulously large and expensive project.

Still you gotta catch up at some point. The product I work on is dropping IE8 in January, which will cause some of our larger and less nimble customers to get stuck on an older version until they can fix their browser situation.

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

#66

Post by dmethvin »

tambourine_man wrote: post #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.

What do you mean dropping IE8 support? The jQuery Core team still supports IE 6, 7, and 8, and has not announced that they are dropping it. That's what jQuery 1.9 is about.

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

#67

Post by jarcoal »

davidlumley wrote: post #47
wycats wrote: 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?

It doesn't normalize DOM events, which is a big one for many people.

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

#68

Post by mcantelon »

estel wrote: post #42
chris_wot wrote: post #37

Earlier quoted context omitted.

What is stopping those users from using Firefox?

Corporate; awareness; familiarity

Those are bad reasons to hold the web back. They don't adapt because they're lazy or don't know better. Making it hard to use obsolete browsers is doing them a favor. They'll like the present when they try it.

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

#69

Post by jlarocco »

tambourine_man wrote: post #60
wycats wrote: 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.

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.

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

#70

Post by MatthewPhillips »

jlarocco wrote: post #69
tambourine_man wrote: post #60

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.

You shouldn't assume that everyone with money or education shares all of the same interests as you.
Post reply on HN