Why is IE6 Such A Big Deal?
07/25/09
The writing is definitely on the wall for IE6. Some major sites and services are starting to drop support for it. Even so, I keep hearing the argument that IE6 must be supported because a good chunk of corporate America is stuck with it. From my understanding, they’re stuck with it because they have propriety web apps that only work in IE6.
From my understanding, they’re stuck with it because they have propriety web apps that only work in IE6.
Ok, fine. But maybe we’ve been approaching this the wrong way the whole time. Why can’t these companies install Firefox, or Chrome, or Safari alongside IE6? Tell employees to use IE6 for their stuck-in-time web apps, and a normal browser for everything else. What’s the problem with this approach? And why aren’t more people advocating it? What am I missing?
Contact & Miscellanea
Send mail (and big checks, if you’re so inclined) to:
PO Box 7919
Boulder, CO 80306
Email:
Add the studio on VIRB° (we’re friendly)
Visit the main site (includes pretty pictures!)
Stalk Follow me (Grant) on Twitter
If you’re a client, login here
So, umm, please don’t steal anything. It’s all Copyrighted ©2006-2010 gb Studio, llc / Grant Blakeman. My personal views do not reflect the views of my company, except when they do. You figure it out.
Comments
JGrubb
From my own limited experience:The machine side:
In my office it’s not web apps, it’s native apps. I work part-time in a call center – the place you call if your Samsung TV goes out the week before Super Bowl Sunday. There are somewhere around 4 or 5 different models of computers that are present on the entire network, with probably 120 computers total. There are probably 40 or so computers that are P3s running Windows 2000. They are not capable of running XP, and Windows 2000 is not capable of running anything newer than IE6. Furthermore, these machines have been completely “brained” into Citrix clients, which do nothing more than connect with a server in the server room which then carries out all the computing tasks of the entire system.
There are another 30 or so “thin client” devices in the Citrix system that don’t even have hard drives in them, they exist only to log into the Citrix server. They only run what is on the main server, which unfortunately has to be IE6 for reasons stated above.
The remainder of the computers are perfectly capable of running IE8, ie. running XP. However, the hodgepodge of software that is tying this place together is constantly teetering on the edge of spontaneous incompatibility with the hardware that’s it’s been installed on for years. In other words, it’s a miracle that this place runs now the way it is, and IT is pretty much busy keeping up with the phone system (it’s a call center), keeping the network flowing, and constantly troubleshooting someone’s machine. Almost all the software is integrated with everything else via widgets and shortcuts, so to take one of the pillars of that system and switch it out is not something that can be done overnight or even over a weekend (even if the place weren’t 24/7, which it is).
The human side:
We are lucky to be in business for ourselves, or perhaps it’s for these very reasons that we are in business for ourselves. We like to tinker. We aren’t afraid of trying different browsers or editors or OSs or whatever the heck, but most casual computer users aren’t that way. People who go to a cubicle every day and work on a computer are absolutely not that way. If one little bookmark disappears or the widget shortcut that opens Excel isn’t there one day or is on the left side of the screen instead of the right, if the most miniscule thing about their workflow changes people completely lock up. I can’t imagine the insanity that would ensue were we to attempt to upgrade all 120 computers in one fell swoop. Most IT folks just aren’t paid enough and have their hands full trying to keep the office running as is to worry about it. I presume…
The corporate side:
It’s probably different elsewhere in the world, but the shop I work is pretty over the top with the Office Space shit. Workers are expected to punch in and be at their cube within 2 minutes. They are expected to be off the phone for no longer than 8 minutes in between calls. Supervisors are constantly monitoring “for quality assurance purposes”. The turnover is constant. The training lasts for two weeks before they even get that far. Bandwidth is constantly bottlenecked. Extra-curricular browsing is discouraged, to say the least.
I can assure you that the higher ups in the office have no interest in changing a single thing about this arrangement. Sad but true.
Andrew
@JGrubb Well to me it sounds like the company is living on “borrowed IT time”. It must be up to each individual company to update and maintain their IT infrastructure. I started a new job a couple of years ago and we pretty much had the same problem but with our servers and services. It’s taken some time but being consistent in telling management how much SH*T is in the systems we have managed to persuade them to invest in upgrading them! And the reason we succeeded is because the company realised that if they wont invest they wont be around in a few years.
gb
John, I think you’ve got some very valid points as to why your company, in particular, has not upgraded much of anything (let alone their browser), but I’m not any of these points invalidates my original thought. In fact, I think they support it.
The case that continues to get made is that corporate IT departments are beholden to IE6 because of policy or software issues. That’s fine, I’ll buy it, but I no longer buy the premise that these corporate IT scenarios should define or set the lowest common denominator for web developers to aspire to. Why not set a corporate IT policy that provides an alternative where possible (notice I said alternative, not default) and accept that premise that some machines (and possibly people) will get left behind until upgrades and retraining make sense to the institution?
The latest versions of Microsoft Office most likely don’t work on a Win 2k machine, and that probably includes features that aren’t backwards compatible with older versions—yet no one complains or expects MS to hold back innovation in that software package. It just doesn’t make sense.
Ultimately, what does make sense is moving forward, but moving forward well. Code well so that things degrade as gracefully as possible in IE6 and older browsers. When it makes sense, provide alternatives for IE6 users. Broken functionality should be minimized as much as possible. But we need to get rid of the expectation that the experience for an IE6 user should be the same as the experience for someone using a modern browser.
Add a Comment