Hmm
Some people might say that anyone using IE6 was still in the stone age. Anyone using MS *anything* might as well be in the stone age. Actually no, scratch that - in the stone age, tools were not prone to being hacked...
A team of ex-Microsoft staffers have set up shop in Blighty to finally wean British netizens off IE6. Browsium has arrived after just a year of doing business in the US. It is making and selling a plug-in for IE8 and 9 called UniBrows, which runs your legacy IE6 apps while letting you ditch IE6. The idea is that UniBrows lets …
So.. you can keep running IE6, and pay $5 per user, and.. keep running IE6 (because if you're tied to apps that were written years ago and are ie6 specific, rewriting them probably isn't going to happen at this stage).
I bet a lot of the Ie6 usage in this country is government - and they're mostly running ancient PCs that couldn't run windows 7 either, so no point in upgrading.
There's no chance of our bank moving away from XP and IE6 any time in the near future (2013 at the absolute earliest, if we start to plan for it now). Which we won't, because we're cost cutting like crazy, and a migration to new platforms, new hardware, and re-jigging all our systems to ensure they work is just far too expensive.
Admittedly, this UniBrow thing would be cheaper, but even cheaper still is just to keep things how they are. After all, our traders are bound to hit the big time and bringing the big money deals, and with them the big bonuses, sometime soon, right? so lets wait until then before green-lighting any project that isn't directly profit related.
The NHS hospital on the Isle of Wight has just done a massive program to upgrade the browser on all machines from IE6 to (drum roll) IE7. Makes you weep how clueless public sector departments are.
IE7 is in some ways worse than 6. Kill it off now and make all our lives easier! Having to put loads of tweaks and hacks into the CSS to get sites working with these ancient browsers is an utter nightmare.
BTW, according to http://en.wikipedia.org/wiki/Internet_Explorer_6 the usage percentages are higher. Over 9% for IE6 and 6.25% for IE7. That's a lot of people who you simply can't write off.
IE Tab for firefox. Which means you don't have to run IE at all except for sites that need it.
Chromeframe, which works the other way around. (Certainly worth putting the line in the HTML header to use this, when it's installed.)
They are both free, and not used that much as far as I can see.
Not surprised at all about the XP statistic - there just isn't good reason to move for many, and many reasons NOT to move for most - but the fact that people still rely on IE working for their business to survive is scary. It was when those programs were written, and it's even more so today.
By all means kill off IE. Anyone stupid enough to still be using that heap of junk, especially for anything business-critical, gets everything they deserve. I believe it's *technically* still on machines that I manage but only because its a pain to remove all traces of it and still be stable. I haven't used it for browsing on any machine for, what, a decade? It certainly doesn't get on the net where I am.
But if you try to kill off XP you will hit more barriers than you expect, especially at a time when IT budgets are falling and XP "has always worked".
I just installed it on a VM and although it's not as bad as I remember it's still blurring the text. This is what I don't understand. I grew up with CRTs and at the time people used to be desperate to get a small enough dot pitch to produce clean and crisp text. Now we finally have LCDs people are using technology that blurs the pixels.
If that's their choice then fair enough but unfortunately I'm one of a number of people who start to feel physically sick with ClearType. It'll be interesting to see if I can tolerate grey-scale SPA but I have my doubts. Something about my eyes/brain just can't handle the concept.
Too damned right.
Fairly recently here, in the comments section attached to an article on migrating to Se7en, some commentard chipped in with one of the most priceless comments of all time.
Their long gestating upgrade from XP project run by ${big_consultancy} had finally turned in its recommendation for the next strategic platform...........32 bit...........Vista!
Next week's white paper: "Glaciation and Continental Drift, the immediate threats to the IT change process.". A study by EDS, Capita, Accenture, etc ad nauseum.....
From my experience, providing web based applications for local government, it is not that the application is written for IE6 - indeed we keep being asked to add web 2.0 prettiness and jquery this and Ajax that - then we get loads of support calls / complaints, 'cos all the users are running IE6 which can't cope with the pretty bits, so we have to spend ridiculous amounts of developer time to provide kludgie work-arounds so the sites look and work ok.
If we mention "upgrading" the local government IT managers have a seizure...
And from the perspective of one of those local government IT managers the reason we have a seizure is because *every other* badly written web application requires IE6 or it won't work. No, we can't upgrade every browser to the latest and greatest version, because then the clinical staff can't do things like get their x-rays etc. This presents "clinical risk", which means we can't do it. Killing people by stopping mission critical apps from working is not considered to be an appropriate way to persuade users to fund upgrades by most operations professionals.
Yes, we appreciate one of the IE6 app's being killed off. No, until or unless your willing to slay *every other* IE6 app we can't upgrade every desktop to any other browser.
"unless your willing to slay *every other* IE6 app we can't upgrade every desktop to any other browser."
Can't you provide a standard environment with *two* browsers?
IE6 for the crapppy written stuff.
Something else for everything else?
Maybe even a software firewall so IE6 can only connect to local IP addresses to improve security if anything can reach outside. Though given its lubed-up nature in Windows that may be difficult...
Most IT departments refuse to do that because it offends their inner BOFH.
IE is the only browser (that I am aware of) that is tied into Active Directory and hence subject to all the user lock down functionality that AD provides.
Put Firefox, Chrome or Opera out there in the hands of the great unwashed and you are forced to rely solely on filtering users at a proxy and lose all the ability to apply "security" policies to users and groups on your network.
Before you know it they would be installing FF plugins all over the place to do all sorts of unapproved stuff.
We need to spend money in order to move away from a browser that works with our line of business applications to a newer browser that has been backwardly buggered to emulate the browser we have that we know works, so that we can then spend more money (and disruption) in upgrading to newer versions of windows?
I am sure there is some logic in there someplace.
So the "right way" is to have everyone download still-insecure code to their desktops, and use it to process still-non-standard web apps? Just keep applying kludges to kludges and never actually fix the underlying problem?
UniBrowse - a layer which sits atop your IEs and makes you look and act like a throwback.
I was HOPING they'd brought consulting services to actually FIX the underlying issues, but instead it's just more lipstick for the pig.
don't forget that when these apps were written ie6 was STANDARD.
if you were writing software for use within a company you wrote it for what you could be certain was on every single machine that would need to access it, with 95% of users on the net as a whole using ie6 and nearer 99% within companies it made more sense to write for ie6 than for any other browser.
also remember that adding workarounds for other browsers that didn't support ie6's way of doing things took extra time (and therefore added costs) so it simply wasn't done.
now 10 years later we have the situation that ie6 is still firmly entrenched in businesses because standards have changed and newer browsers dont work in the same way, companies have a few options.
1. continue to run XP on newer hardware and use ie6 for internal systems with $browser_of_choice for external browsing
2. upgrade beyond XP and get all of the apps modified to support newer browsers (with the extra costs that entails)
3. upgrade beyond XP and find some way of running ie6 where needed for internal work until the apps that need it are retired.
I can see a lot of companies going with option 3 since most of the apps that need ie6 will themselves be coming up to 10 years old and are probably showing their age and are also likely due to be replaced anyway.
"don't forget that when these apps were written ie6 was STANDARD."
Except it wasn't. There were established standards and ie6 was deliberately written to be incompatible with them. (Earlier versions were, to give MS the benefit of the doubt, accidentally incompatible with the HTML and CSS standards, but MS made the conscious decision to make IE6 default to IE5 compatibility, rather than standards compatibility.)
"now 10 years later we have the situation that ie6 is still firmly entrenched in businesses because standards have changed and newer browsers dont work in the same way, companies have a few options."
Correction: standards have, for the most part, NOT changed. Microsoft has (to some degree) given up on trying to change them to their (non-standard) way. This isn't entirely one-sided, however. Some good standards changes were actually begun by Microsoft (XMLHTTPRequest, for example).
As for the options companies have, you've missed one:
4. Investigate whether the app is ACTUALLY incompatible with IE7/8/9 -- I've seen quite a few cases where companies read "IE6" in the system requirements line and gave up without even trying.
In most cases, one could write to the standard and not really fall foul of any IE6/standard problems. It was only when writing (then edgy) CSS styles or (then bleeding-edge) AJAX applications or (sadly all-too-common) crappy browser sniffers that would break even when minor versions of IE were changed that problems arose.
But developers being what they are, they wrote to the bleeding edge, and now we're suffering the bloody consequences.
No mixed picture at all:
two thirds of businesses have not paid any extra money to MS to upgrade their XP desktops to Vista / Windows 7.
MS COO called XP & IE6 "Not making us any more cash - for fuck's sake people give us your fucking money by upgrading an OS you already have to an OS you don't need"
IE 6 and XP are dead, but the same old customers who clung tightly to their aging NT4 infrastructures are repeating the same mistake with XP. And just like back then it'll probably take numerous large scale security vulnerabilites leaving their network wide open and critical applications like Office moving on too far for them to ignore before they'll try and dig themselves out of it. Which inevitably ends up costing far more in the long run.
A horrible thought occurred to me. I think there's still tons of COBOL code written in the 1970s running in big companies.
If you know all the IE6 quirks and can stomach it, you could probably get paid doing maintenance programming, upgrades, and such, for IE6-only websites for a long, long time. Kind of like the current greybeard mainframe programmers... "Say hello to 2038, IE6. Hope you are not experiencing any integer overflows, our CRM use depends on you keeping on running on this VM running in compatibility mode to run this plugin to run you".
I do wonder which is a more developer-hostile environment? 1970s-era programming languages, operating systems, and applications, or IE6?
"Microsoft delivered IE6 a decade ago and despite three successors, it remains firmly entrenched because so many businesses-critical apps in the public and private sector – things like Siebel CRM – were hardwired for the browser at the time."
Now that's what I call lock-in. Shame that MS is not actually benefitting from it though. Hah!
I still use w2k for some things because it works well enough and I don't want to pay for changes that bring no direct improvement to me.
Of course, it runs in a VM now so I don't need to worry about hardware drivers, nor do I use it for email/web browsing/etc so security is much of a headache than when it was new & supported...
Tux, my friend.
I can seriously understanding businesses sticking with W2k. From the users point of view it was the high-point of functionality. For example if you want more fileserver licenses, you could just tell the system you bought n... and it would just believe you.
W2k also had network functionality, like being able to join Windows domains, or providing a primitive telnet server. In fact the larger versions even had a working RDP server.
XP has very little advantages over W2k. It requires activation, it removes vital networking features and it needs more resources. Same goes for Vista and 7.
The only problem is that W2k won't get any bugfixes any more, but well companies typically don't care about security. If they would, they wouldn't run Windows.
Which tree have you just fallen out of?!
My company very much cares about security and it's nothing more than a typical financial trading house with around 1,000 bums on seats. We get the updates of the Windows support mob as often as required and they are about to start user testing Win7 on the desktop as WinXP now has to go.
"If they would, they wouldn't run Windows.", sorry?!
I use OSX home and Linux/Solaris at work, so I personally avoid Windows but I am not so far up my own fundament to even contemplate suggesting that a typical company like run anything other than Windows. Sorry but fact of life, the business world runs on Windows front-ends, quite a lot of backends too when they are not on *nix platforms.
No you shouldn't upgrade for the sake of it but sometimes moving forward carefully is not the end of the world and there are benefits. If we all had that attitude we'd still be up trees picking nits of each other and eating them! Another fact of life, systems need to be kept upgraded to most often ensure support contracts are maintained. You go to MS right now and say something in W2K is not working properly and they will most likely say, "Well tough luck I'm afraid. Check the MS support forums else you will have upgrade, sorry!".
W2k was the first and last good OS that came out of Redmond. Especially because you would use *nux file, print and DNS servers instead of cheating on the licenses.
It is true that the move from w2k to wxp was proof of deep stupidity. Apart from USB2, XP had absolutely NO advantage over 2k, only disadvantages - just plain proof that WIndows admin = cretin! USB2 has absolutely nothing to do on a work desktop ...
I have yet to come across a Windows Admin with any sense whatsoever, counting out *nix admins with too small balls to convince management and forced to administer wincrap.
Once you take the *nix pill, you are outside the matrix ... free as a bird. I understand, though, that for n00bs, it's scary to leave the matrix.
"USB2 has absolutely nothing to do on a work desktop ...
Looks at external drive. Looks at thumb drive. Imagines what would happen if they were connected by USB 1.1. Looks at post obviously made by complete cretin. Sighs.
"Once you take the *nix pill, you are outside the matrix ... free as a bird. I understand, though, that for n00bs, it's scary to leave the matrix."
Ah. So Mac OS X is outside the matrix and free as a bird, eh? Nice to know. You _do_ know that OS X is a 'NIX, don't you? It uses the Mach kernel, and is based on FreeBSD and NetBSD. However, 'free' is one thing that it ain't. Looks at post, now conclusively shown to have been made by complete cretin.
Telling giant companies "just upgrade" is a huge ask for the obvious reasons already mentioned. But having them stick with IE6 for existing apps means new apps will likely also require or be limited to what IE6 offers.
This kind of solution (also the Chrome/FF tools) lets you develop new apps for modern environments and upgrade old ones as convenient, rather than being an all-or-nothing decision.
You'd think the company would market to China though.
My gut tells me a bunch of this is to do with specialist apps (Siebel and some kind of X ray viewer for hospitals have been mentioned so far but I'll bet there are a lot more).
Until they *all* change (IE all that are used by a particular environment EG NHS, local govt, etc) the *cheapest* option is to not move.
Customers *let* themselves be f**ked back then. They should know better now. At least put contract requirements in to say the supplier has to compatibility test for later versions of Windows. Better yet *insist* on open standards. WTF are things *not* browser neutral these days?
That's what you get when you've got 1 supplier who can supply an app to do this.
You think you own the supplier. The reality they own you.
MS created a browser with broken proprietary features, got everybody to write software for it, and the worst is, most companies did and have been stuck for a decade. Why anyone would want to make business with a company like that again, I don't know ... masochist n00bs!
Here comes the guy who is co-responsible for the mess and tells you he will gladly tie you in for another decade ... bet most companies will open their arms and let the fellow in ...
He who has not switched to Linux by now is an idiot and should leave the profession immediately, no "ifs", "buts" or "maybes" ... Do your job correctly ... I keep hearing mere idiots bringing invalid arguments like .... eehhh we have 6000 desks to migrate blahblahblah ... The transition MS Office 2003 to OpenOffice or whatever is WAY cheaper than the transition MS O 2003 to 2007 or 2010, same goes for Windows ... XP to Vista or 7 is just as hard as XP -> Linux.
The main culprit from my experience is the public sector, the NHS still has a very high percentage of computers running IE6 due to legacy applications. I somehow doubt that the NHS is going to spend any money in upgrading thousands of computers simply to see mainly external websites in their full splendour!
Back then, browsers weren't all magical like now. IE6's proprietary features were pretty neat and let you do cool stuff which managers probably demanded so they could "have apps in the browser".
I get this kind of demand for 3D graphics - everything has to be "in the browser" these days regardless if it makes any sense.