Live data from Hacker News

JQuery 2.0 Released

blog.jquery.com

61–70 of 226 posts

Re: JQuery 2.0 Released

#61
post #48

Earlier quoted context omitted.

At the speed web development is moving, I don't see much sense in coddling browsers that are more than 2-3 years old.

Naturally that depends on your target audience. I haven't checked the version, but we're stuck on an older IE at work. Possibly 9, but I think it's 8. No choice in the matter.

"No choice in the matter."

Does someone have a gun the CEO's head stopping him? He could tell everyone to install latest Chrome or Firefox and have everyone upgraded in 10 minutes.

Re: JQuery 2.0 Released

#62

I cannot believe IE8 is now considered 'old'. It is the second most used browser+version on our site, and has about 80% as much usage as the leader, IE9. Can't see IE8 support being droppable for many years yet.

Checked the stats on my site. Based on around 50,000 unique visitors yesterday, 3.7% used IE, and 0.5% used IE 8 or below. It's related to technology though, so it's skewed highly towards firefox and chrome.

Re: JQuery 2.0 Released

#63
post #11

I wish Microsoft would shoehorn at least IE9 into XP, maybe like Chrome Frame. It's crazy how many people are still stuck with XP/IE8 which is a massive web dev headache.

My favorite is how it fails to support decade old features like DOM Level 2 and XHTML.

but nobody gives a shit about xhtml

Re: JQuery 2.0 Released

#64
post #34

Earlier quoted context omitted.

Even IE9 is pretty old. It's over 2 years old by now. IE8 is over 4 years old. IE11 will be released soon. How many versions of IE do you intend to support?

We have clients who still use IE 6. BIG clients - banks too big for me to name publicly. Millions of dollars in revenue and dozens of jobs' worth. Dropping them isn't an option.

Then don't drop them. This is for modern websites/services, not enterprise catering dinos.

Re: JQuery 2.0 Released

#65

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?

I do.

The final 2.0.0 file is 12 percent smaller than the 1.9.1 file, thanks to the elimination of patches that were only needed for IE 6, 7, and 8.

Dropping IE 6, 7 and 8 support for a 12% smaller file size while effectively forking your code base for the foreseeable future is a lousy decision. Increase complexity tremendously for what, 3-4 KB when gzipped?

Re: JQuery 2.0 Released

#66
post #44

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…

I don't work on jQuery any more but I (and I know many others on the jQuery team) all build web sites as part of their day jobs (and, thus, need to continuing supporting IE 8). It's going to be a very long time before support for the 1.x branch is dropped. But hopefully soon, death of IE 8 willing.

Is there any list of companies that currently require old versions of IE? I know a lot of hospitals do, and people handwave banks and whatnot.

If there was a big list of "These people still use old versions of IE", then we could:

  A. Properly shame/advertise for attack/avoid getting work from these people.

  B. Expose a dedicated market audience for compatibility-minded dev shops
Either of these would seem to be a Good Thing (tm), and would help remove a lot of the FUD in the ecosystem.

Re: JQuery 2.0 Released

#67
post #14

Earlier quoted context omitted.

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.

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

On the contrary. Lots of big volume mainstream websites (including even Google properties) have stopped supporting IE6 and some even IE7 for years. For IE6 it has been at least 4 years since most sites stopped caring about it.

(Heck, even Microsoft created a site to convince people to drop IE6 it last year).

Mainstream websites will move much faster off of IE8. It's enterprise shops and people making software or websites targeted at them that will take the longest.

Re: JQuery 2.0 Released

#69

I cannot believe IE8 is now considered 'old'. It is the second most used browser+version on our site, and has about 80% as much usage as the leader, IE9. Can't see IE8 support being droppable for many years yet.

Our users:

IE8: 40%

IE9: 25%

Chrome: 15%

Firefox: 10%

iOS: 5%

Others: 5%

The majority of our clients are businesses with 50 to 500 employees in Australasia.

Re: JQuery 2.0 Released

#70
post #48

Earlier quoted context omitted.

As many versions as used by the audience that they serve I suppose; how is the choice up to him?

At the speed web development is moving, I don't see much sense in coddling browsers that are more than 2-3 years old.

I think this really depends on your target market. Big corps such as banks are typically slow to move and I know of at least one which is only just moving from IE6 now.
Post reply on HN