71–80 of 226 posts
Earlier quoted context omitted.
From the post: "...we’ve got jQuery 1.x to handle older browsers and fully expect to support it for several more years."
Exactly. What does "several" mean? Are we talking two years? Five? A decade? Until jQuery changes their minds?
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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…
However, I (not speaking for the company, just me personally) strongly disagree with the focus on "identical experience" amongst browsers. Instead, I prefer the route of graceful degradation where not all features may be available for all browsers, but it's fully functional and aesthetically pleasing (not necessarily identical) in all browsers.
That being said, not all companies have the same browser support requirements...it's entirely based around what the site's individual traffic and conversion rates are.
So if the Query team is still going to support these browsers in 1.9, why even make the 2.0 version?
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.
I'm annoyed XP doesn't have IE 9 or DirectX 10+, but I guess that's Microsoft's way of getting people to upgrade to newer versions of Windows. Based on current stats, I'd say IE 8 hasn't got long till you can ignore it but it really depends on how much market share you care about. Do people STILL target IE 6? IE 8 is on ~10%[1] and at the current rate it's dropping at should be at 5% by October - Just in time for IE…
Earlier quoted context omitted.
It looks to me like he's worried (or saying that other people are/might be worried) about how long 1.9 will continue to be supported for.
From the post: "...we’ve got jQuery 1.x to handle older browsers and fully expect to support it for several more years."
Earlier quoted context omitted.
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…
They have applications that need to be managed by what is undoubtedly an outsourced IT service, very likely related to some other system (practice management, diagnostic hardware, goofy industry-specific file formats, accounting, back-office, etc.).
They will stay on XP for ages because it works with everything they bought when they last "modernized" their practice ten years ago. Upgrading will be prohibitively expensive, on the order of making the decision to hire one junior staff member for a year.
The same upgrade will cost the same in a year, or five years, so there's no business purpose to upgrade until they need to migrate to another platform, either due to lack of support for modern hardware as the existing gear ends its lifecycle, or because of a strategically imperative application that requires an upgrade.
They may need enough "modernity" in their web browser for industry sites and (increasingly) wikipedia, but most uses of web 2.0 will be shrugged off as inessential, whether it's Facebook or Highrise/Salesforce/whatever.
Bigger companies have to refresh hardware due to failure at a higher rate. As a result, they can retain a permanent staff of people who manage OS images and upgrade on a next-to-last type cycle. Smaller companies are often using "personal" grade equipment and will take the accelerated depreciation when they need to buy one new laptop because the old one is too slow.
Earlier quoted context omitted.
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…
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.
As for "identical experience", I will have to disagree. I have no problem with gracefully degrading sites due to screen size or compute power, but there is no reason that desktop browsers should be permitted to render things differently from one another (and if the spec is ambiguous, we should fix the damn spec). Developers are lazy, or shortsighted, or both, and given the option of "Hey, works on my machine/browser/whatever", we should expect only annoying fragmentation.