April 8, 2010
According to today’s statistics Microsoft Internet Explorer v.6 has dropped to 8.9% share of browser usage worldwide (have a look at www.w3schools.com for the latest stats – it might be even less by the time you are reading this).
This has prompted us to make a decision which we have been agonising over for quite a while: by default we are not going to support it any longer.
Why? Well, in short it doesn’t really work. We have to do things to our websites that we’d rather not do to make them work in IE6 – things that often break the site in other browsers.
That’s an oversimplification, of course. IE6 was OK in its time. But its time has passed. Things we take for granted just didn’t exist in August 2001 when it was released. No PNG transparency, lack of proper CSS support, non-standard rendering of pages and bugs galore were not so much of a problem when there were no standards to stick to. However, times have changed and browser manufacturers – despite still arguing about details – are making an effort to standardise the way websites display and work in order to deliver a better user experience.
The Web 2.0 revolution that has happened since the release of IE6 depends on technologies that just don’t exist in that browser. Neither YouTube, Facebook, Twitter or Google want anything to do with it any more because they don’t want to be held back. Other browsers allow them to move forward and innovate.
The biggest problem we have is that we are constantly told that “large corporations” still use IE6 because their IT departments insist upon it. We’ve never actually seen proof of this but we do come across clients who have shown their new site to somebody who is still using IE6 only to see it break or just look plain ugly. This, of course, makes us look incompetent. The hacks we need to do to avoid this often cause a huge amount of lost time as it involves actually finding out what the problem is first before embarking on a long quest around the internet to find a solution which doesn’t have the opposite effect on the other browsers. Then we have to actually implement that solution. Naturally the incompatibility is usually spotted at 4:45pm on Friday.
If we allow for this when quoting for work our prices will look expensive. If we don’t and take the chance everything will be OK, we’ll probably lose out. It’s always a dilemma.
We’ve read endless tirades against IE6 and why it should be killed off. Calls on discussion groups for militant action and rants and raves (which just usually end in general Microsoft-bashing), usually made in the early hours of the morning by web developers who are at the end of their tether trying to make their site work in a crappy, obsolete browser and not getting paid anything for it, whilst trying to explain to clients in simple terms what’s actually going wrong. We understand this – we’ve been there ourselves.
But mouthing off on the internet isn’t going to help, so we’ve decided to do something a bit less confrontational and, hopefully, helpful.
We’ve decided to make IE6 support an option with the websites we build. From now on our quotations for web work will have an “IE6 compliance” line which will detail the extra costs involved in making the site backwards-compatible for this browser. It’s not a way of charging extra…believe me, we’d really rather not have to bother supporting IE6 at all – life is just too short. But we can and we will if we have to. This way the client has the option. Long term, we hope if more web development companies calm down a bit and do the same IE6 will just become a ghost in the browser’s graveyard along with AOL, Netscape, Mosaic and CyberDog.
We’d like to hear people’s thoughts on this approach.
