Does IE6 Still Matter?
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?
If you want to get a rise out of any Web developer, just mention support IE6. It won't take you long to find programmers posting comments like, "IE6 blows up the navigation, which appears as expected in IE7, FireFox, Opera and Navigator." Everyone knows that IE6's notion of "standards compliance" is as dependable as a politician's promises; yet, supporting the older browser consumes a vast amount of developer time, arcane #ifdefs and eyes of newt. Not to mention cusswords. Lots of cusswords. ("The amount of CSS and JavaScript hacks we had to pull off [to work in IE6] was enough to make you scream," wrote one developer.)
It's particularly irksome to spend a lot of time and energy testing your apps against software that's going away (in some opinions not fast enough). The question is: when is it time to quit IE6 support? With IE7 now leading the Internet Explorer brigade, and Microsoft promising to support IE6 until 2010, at what point can you tell users, "If you're using IE6, it's your own tough luck?"
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.
Previous Post: Choosing the U.S. CTO: Who Would You Pick?Next Post: 6 Stupid Mistakes Companies Make with Their Online Communities
Most Discussed Posts
Cloud computing has emerged as one of the most significant game changers to hit the technology landscape in the past 20 years. With this massive expansion of the cloud, the perception of the IT organization is shifting from a utility player to a change agent. This eBook breaks down five ways progressive organizations are using cloud-based IT Management solutions to help drive innovation and become more strategic, including: adding visibility and analytics, speeding up time-to-value, lowering costs, improving prioritization, and providing a blueprint for future cloud deployments.
Read the white paper to see how IBM helped Citigroup deliver new services and enhancements to their 200 million customers faster.
There are 3 ways to modernize legacy applications: rewrite completely, acquire packaged solutions or migrate existing code. This paper explains why it's best to migrate and how IBM® Rational® software can help.
Accommodating specific lines of business can result in a hybrid ecosystem of applications and servers. The resulting complexity of this architecture makes for an environment that is costly to maintain and difficult to change when addressing new challenges.
This whitepaper will help you to define a mobile device passcode policy. Security managers must attempt to reconcile two opposing goals. They must: 1) create a passcode policy that is strong enough to protect the device if it is lost or stolen, while: 2) not annoying users with needless length or complexity.
This whitepaper, authored by The Radicati Group, looks at the key reasons organizations should consider moving to a cloud-based archiving solution. Email archiving solutions enable organizations to store, monitor, and collect electronic data exchanged by their users to comply with internal policies and regulations.
ATERNITY will showcase a 30-minute demo on how Fortune 500 companies are leveraging its award-winning FPI Platform to deliver a user-centric approach to Proactive IT Management.
For businesses to move forward and tap into the ever-expanding universe of Internet users and network-enabled devices, it's critical to learn how to make the transition to IPv6. Learn the critical steps your organization must take to make a seamless transition-and keep your business world connected.
Learn how IT teams can protect against spear phishing tactics. Harry Sverdlove, chief technology officer of Bit9 offers a frank discussion about spear phishing - the most common technique used in today's advanced attacks.
Learn how to build a solid business case for your migration to Red Hat Enterprise Linux so you can run leaner, innovate faster, be more flexible and own the New Now.
Social media isn't about you; it's about everything around you. As you consider how your customers want to communicate with you, social media is something that can't be ignored. But what should your strategy be? Is social media "just another channel?" What kind of a plan makes sense for your contact center and for your customers? Join our experts as they share their insight and research results.
Hardware tokens were a popular method of strong authentication in past years but the cumbersome provisioning and distribution tasks, high support requirements and replacement costs have limited their growth. The additional log-in steps that hardware tokens require and the resulting user frustrations have limited adoption and make them impractical for larger scale partner and customer applications.
Sponsored Links
