If you develop for the web, you know IE6. The default browser that ships with Windows XP is the bane of any "standards-based" developer. For public web site developers, it adds days- if not weeks- to development cycles for testing and tweaking site functions to work in the ancient "broken" browser. If you work in a company still running XP and IE6, you may not notice the problem today, but eventually your sites will have to say goodbye to IE6, and with that transition will come your introduction to the pain the rest of the world has suffered.
Tuesday, February 02, 2010
There have been public initiatives for years trying to get companies (almost all "home" computers auto-upgraded via Windows Update to IE7 years ago) to ditch IE6. Sites like IE6Update.com and BringDownIE6.com try to educate and provide an easy upgrade path for users stuck on 6. But after more 9 years, IE6 still holds a 22% global market share (to IE7's 17% and IE8's 19% in Q409).
Many famous sites have already reduced support for IE6, calling it "unsupported" and providing a reduced or "non-guaranteed" experience. Apple, Facebook, and YouTube are some of the higher profile examples to-date. Now Google is turning-up the heat.
I received an email as an administrator of a Google Apps for Domains (Google's business-oriented service platform for its apps) account that included the following message:
In short, Google is ending support of IE6 for it's major business apps, like Gmail and Google Docs, this year.
This will clearly help accelerate the end of IE6's relevant market share, but it also opens some critical questions. Why doesn't Microsoft adopt the same aggressive stance for its own web apps? For Silverlight? Do you need to support IE6 in your own public web apps?
While we can all hope for a day when web standards will unify to a level that we can really embrace the power of HTML5, Telerik will in the mean time continue to support IE6, as we recognize that some of you may be "trapped" in IE6 organizations. This obviously adds a fair amount of overhead to our own development process since it makes adding new features more difficult, but we are committed to supporting the needs of our customers. While the rest of the world calls IE6 unsupported, Telerik continues to work hard to help you support it if you must.
But what do you think? Is IE6 still relevant to your development? Or can we all agree to join Google and make 2010 the year we say goodbye to IE6? Let me know. I'm always listening.