Microsoft’s Internet Explorer 6 is seven years old. It’s a pain to write Web applications to run correctly on the notoriously non-standards-compliant Web browser. Should you bother? Do you?
This is not an idle issue. There’s an active discussion in one list I lurk on (which happens to be for open source evangelists, not for Web developers per se); the open source project’s site doesn’t work correctly in IE6, so it may be chasing away would-be users. About 25% of Internet users run IE6, representing more than all Firefox versions (assuming you trust anyone’s Web browser statistics)… well, that’s not small change. With IE8 on the horizon, increasing relevance of mobile Web sites and new browsers like Google’s Chrome to support, that spells a lot of developer software customization time.
Obviously, every site has its own target user. If you run a consumer e-commerce site, and only 10% of your users run IE6, you have to support them because you don’t want to reduce your revenue by 10%. (Somehow this logic has escaped some e-commerce sites where I might otherwise shop, but let’s not go down that path.) If you’re developing departmental in-house software to run only on your Intranet, you can pay attention to the corporate standard Web browser (at whatever patch level the company blessed) and ignore or sneer at the hoi-polloi who use unsupported browsers. Most sites, however, are somewhere in between.
Which brings us to you. What are your plans for browser support? When will your shop decide that it’s no longer worth the time and energy to retrofit your cool, new standards-compiliant and Ajax-heavy website to support IE6 users? If it hasn’t happened already, tell me what will force the change… and take our short poll to compare your opinion to other users.