Until Windows XP is banished from corporate machines worldwide, I don't think we can drop IE8 support. (You can't install 9/10 on Windows XP.) I'm glad they decided to continue support for 1.x for now.
[deleted]
JQuery 2.0 Released
101–110 of 226 posts
Re: JQuery 2.0 Released
#102This is a welcome change. Considering the market share of IE 6, 7 and 8 is pretty minuscule and Google dropping support for IE8 back in November 2012 should be cause enough to drop it from jQuery too. It's great to hear they'll be supporting the older 1.9 branch for users who need to support older versions of IE as not everyone has the luxury of being able to ditch older versions of IE like that. There's no cause for…
Is 31.37% pretty minuscule? I don't think so... Source: http://www.netmarketshare.com/
It is if your customer base are comprised of very few IE users.
Re: JQuery 2.0 Released
#103Earlier quoted context omitted.
You're missing an important part of this. There's a large number of companies whose web capabilities need to support people who use their website while working at the companies that have older versions of IE. The company I'm with has embedded video players on a large number of web retailer's pages (we're hiring a javascript+flash developer in Austin, TX right now, particularly around video players. If you're interest…
There's a large number of companies whose web capabilities need to support people who use their website while working at the companies that have older versions of IE. Like who? Honest question. I know that not all users currently have modern browsers (which is total bullshit, by the way--with free, open-source browsers as well as Chrome and the like, there is no excuse for this) but this isn't something we should tre…
There are thousands of users in major banks and financial institutions which still use IE and have NO plans on moving forward anytime soon. None.
I don't mean the users. I mean the companies. You really think the banks that LITERALLY control the world's economy are somehow going to be 'shamed' into upgrading their internet browsers? You might as well try shaming the moon into changing color.
I don't mean to sound condescending, but there's no other way to put this...the comments about browser support on this board show just how inexperienced many developers really are. We are not talking about installing Firefox or Chrome on a few PCs. We are talking about MASSIVE companies with BILLIONS (with a 'B') of dollars flowing through WORKING systems that have been tested into infinity and are the backbone of our economy. Should they upgrade? Sure. Will they? No. not until they've stretched the technology they are already running until it collapses.
This move by JQuery devs, I get it, but it's quickly pushing itself out of the realm of 'awesome' to 'annoyance', only suitable for small projects. I hope not, but that's what it looks like. Even 1.9.x deprecated some features that should have been left alone - we had to code them back in.
Re: JQuery 2.0 Released
#104I 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.
I cannot believe IE8 is now considered 'new'. It is the least used browser+version on our ecommerce site. Can't see IE8 support being a priority for many years.
FWIW, I'm not joking.
Re: JQuery 2.0 Released
#105This is a welcome change. Considering the market share of IE 6, 7 and 8 is pretty minuscule and Google dropping support for IE8 back in November 2012 should be cause enough to drop it from jQuery too. It's great to hear they'll be supporting the older 1.9 branch for users who need to support older versions of IE as not everyone has the luxury of being able to ditch older versions of IE like that. There's no cause for…
Is 31.37% pretty minuscule? I don't think so... Source: http://www.netmarketshare.com/
As best I can see on the site you linked, IE8 is 23.23%. That also disagrees significantly with this source: http://caniuse.com/usage_table.php where IE8 is 8.89%
Re: JQuery 2.0 Released
#106This is a welcome change. Considering the market share of IE 6, 7 and 8 is pretty minuscule and Google dropping support for IE8 back in November 2012 should be cause enough to drop it from jQuery too. It's great to hear they'll be supporting the older 1.9 branch for users who need to support older versions of IE as not everyone has the luxury of being able to ditch older versions of IE like that. There's no cause for…
Is 31.37% pretty minuscule? I don't think so... Source: http://www.netmarketshare.com/
You combined all aforementioned versions of IE together to yield that result: http://www.netmarketshare.com/browser-market-share.aspx?qpri... — even combined the market share is still in my opinion minuscule. The only browser with a substantial market share is IE 8 which according to the site has a market share of 23%, it's not even worth adding in those other percentages on-top to try and make it seem as though a lot of people still use those browsers.
31% is not justification enough to maintain legacy code in a library that has become a little bloated over the years because of the backwards compatibility with older browsers. If you want to support that 31%, use the 1.9 branch it's better than the alternative being no support whatsoever.
Edit: Why all of the down-votes, is my response offensive?
Re: JQuery 2.0 Released
#107Earlier quoted context omitted.
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?
Actually, it's decreasing complexity and getting a happy side effect of a 12% smaller file. It was probably a mistake to add the file size difference as a benefit, as it has obviously confused a lot of people who appear to have perceived it as a primary design goal.
I'll say the size drop is the primary reason I'm going through having the browser tags for ie lt 9, vs other... even though 3-4K isn't much, that's quite a few packets on mobile (though there is Zepto, it's nowhere near complete enough for a lot of needs).
I'm working on some revamped UI at the moment, and so far the script load (uglified, not gzipped) is around 250K, anything that can get that down imho is a good thing.
Re: JQuery 2.0 Released
#108Earlier quoted context omitted.
It all depends on your end goals and your audience. I don't have #'s off the top of my head, but let's say IE8 accounted for 40% of browser usage across your visitors. But IE8 is old. Are you willing to say to 40% of your potentially paying customers "Sorry, but your browser sucks. We're not supporting you."? If you are, great. No coddling necessary. But for other people, they may not be comfortable with the percenta…
You wouldn't say it like that, I hope. You would say, “Here's a link to a browser upgrade that will allow you to enjoy the best product we can offer you. It's completely free, and takes only a few minutes to install!” Also, IE8 accounts for less than 10% of browser usage worldwide now, so the odds of a company having it be 40% are rather slim, unless they specifically target enterprise in which case they dug their ow…
Oh no, of course not. I'm just trying to make the point that some companies may not be comfortable with whatever IE8 is at right now. I think you can substitute "IE8" for any browser, and "40%" for whatever that browser's current market share is.
Coincidentally, I work in the multi-family housing industry, and one of the industry titans requires IE to use their product--which everyone uses--so we have ~82% IE share on our own product (which is supplementary to the titan). Of that, IE8 stands at ~31% of our total site traffic, which is compelling enough for our company to need to support it. (IE9 is only ~39%, with IE6/7/10 making up the remaining 12%.)
So until that industry titan changes their way, we're stuck in an IE rut.
Re: JQuery 2.0 Released
#109Earlier quoted context omitted.
You're missing an important part of this. There's a large number of companies whose web capabilities need to support people who use their website while working at the companies that have older versions of IE. The company I'm with has embedded video players on a large number of web retailer's pages (we're hiring a javascript+flash developer in Austin, TX right now, particularly around video players. If you're interest…
There's a large number of companies whose web capabilities need to support people who use their website while working at the companies that have older versions of IE. Like who? Honest question. I know that not all users currently have modern browsers (which is total bullshit, by the way--with free, open-source browsers as well as Chrome and the like, there is no excuse for this) but this isn't something we should tre…
For the 'Like who?', I'm too lazy to check which companies are our customers that have a "can be used to endorse our service" clause, the categories off the top of my head are: major telecom providers, major PC sales companies, office furniture sales companies, major clothing companies, major beauty product companies. Note that this doesn't cover new companies or technology focused ones, there's a particular demographic that they are selling to that at a minimum browse their sites while at work. And after rereading everything, I may have been a bit ambiguous, so I'll clarify. People, while they are at work, use browser A because they work for shitty company X. While at work, they browse, add to cart and buy from an unrelated company. And for whatever reason, people buying from the unrelated company are disproportionately doing so while at work and working for a company with outdated browsers.
For the degradation, I especially don't mean a lazy approach. In fact, having good degradation is typically harder for newer developers (or requires them to check in more browsers). The core way to do it is to develop for what's common across browsers (what's handled the same way), then for ambiguities in the spec (does the border count as part of the width of a div or not?). Once that's done, you then add the extra. The idea is, if browser A supports, say, easily defined gradients on a button, but browser B doesn't, should we have a special case for browser B to load an image to give the identical gradient, or should we let it be a flat colored button? Or let's say a browser has some extensions that make client-side form validation easy and simple. Using that functionality for that browser makes sense, but is the development effort to do the validation on all browsers worth it when server-side validation will happen also? The functionality is the same, the experiences are both good, but the experiences are not identical.
Re: JQuery 2.0 Released
#110Earlier quoted context omitted.
You wouldn't say it like that, I hope. You would say, “Here's a link to a browser upgrade that will allow you to enjoy the best product we can offer you. It's completely free, and takes only a few minutes to install!” Also, IE8 accounts for less than 10% of browser usage worldwide now, so the odds of a company having it be 40% are rather slim, unless they specifically target enterprise in which case they dug their ow…
Oh no, of course not. I'm just trying to make the point that some companies may not be comfortable with whatever IE8 is at right now. I think you can substitute "IE8" for any browser, and "40%" for whatever that browser's current market share is. Coincidentally, I work in the multi-family housing industry, and one of the industry titans requires IE to use their product--which everyone uses--so we have ~82% IE share o…
That's a shitty situation to be in. Sounds like a great opportunity for someone to disrupt that industry titan, though.