To Advocate For or Abandon the 10%

Back in 2002 or 2003, when Internet Explorer reigned at the undisputed leader in browser market share, I was very outspoken over the need to support all browsers – even those with only 5% share or less. I argued about the need to provide a consistent experience for all users, regardless of what browser or version they decide (or as forced) to use. This ideology was all the easier to adopt considering how had market share at the time – I feel as though my strong feelings were just as much about not idly allowing the “evil” corporate browser to swallow even more share by helping make it the de-facto browser on the internet. Fast forward 5+ years and oh, how the tables are turning. A new generation is jumping online and they’re not just blindly clicking the blue ‘e’ on their desktop. Firefox 3 shattered the record for most downloads and, according to some metrics, is passing up 20% global market share and well above 40% in some European countries. The underdog is now the up-and-comer.

Which brings me to why I am writing this article. I am in the process of putting ideas and concepts together for the redesign of somerandomdude.net which has taken me down some very interesting paths. The problem is, many of these ideas are simply not going to work on older browsers – most notably, Internet Explorer 6. IE6 still comprises roughly 10% of the traffic on this site, which should be far too significant to ignore. Here is the conundrum – I just do not seem to care. IE6 is, by current standards, a train wreck of a browser. I have seen more web projects than I would like to remember use the majority of their production time just to resolve IE6 issues. Still, I fail to see the philosophical difference between supporting the Netscape 7′s in 2002 and the Internet Explorer 6′s in 2008. In fact, IE6 gets more share now than any of the browsers I fought to support did. All that said, I still am leaning towards not supporting it.

My argument towards not supporting IE6 for the new redesign would mean faster production time, and allow me to use publishing methods which would help me post much more frequently. So here’s the question – do ends justify the means or is this just an example of hypocrisy at its finest? My justification is continuing to support IE6 will limit what I can do to the blog (in the time I have to build it) in order to make posting easier – which should allow more content to be published. So, do I continue to give an equal experience to the 10% or give an improved experience to the 90%? This question is not new by any means, but I find myself on the other side of the argument this time.

What are your thoughts on this? Does creating a consistent experience trump a better site for the majority? Do the ends justify the means? Should a compromise be found?

The Discussion

9 Comments

  • It seems that its a different question this time because IE6 is outdated itself. Its not like you are cutting off the whole “internet explorer” community but just forcing some people to finally upgrade to IE7. It is their own choice to switch browsers, you are just pushing them to stay current.

  • Hypocrisy at its finest :)

    But guess what? I did it too not long ago! In my case it’s a developer-oriented site so IE6 % is even lower AND i do NOT feel guilty at all for developers (listen, developers!) still using IE6 as their *primary* browser.

    Zarate’s last blog post..Wubi

  • making decisions is really tough but we need to make one. users will soon change to a newer browser and it will happen, those 10% knows they need to cope up with this change and surely see your justification. go on give the 90% the best you can.

    bleuken’s last blog post..Busby Blog and Capiz Chess Blog

  • Making charitable donations is one way that people can feel good about paying it forward. Donating to organizations that promote programs for the people who need our help makes all of us feel much better!

  • I trully believe that blogsfera is able to contribute for the strenghing of the social support through donation.

  • At some point, people with 8 bit screens, 640×480 resolutions and IE6 browsers should be abandoned. IMHO, it’s not that big a deal since they are used to whatever crappy web experience they are getting with their outdated tools.

    Why bend over backwards, and probably hurt the experience for 90% of the user to protect the 10%, especially when IE7, IE8 beta, Safari, Opera and FF3 are all available for download.

    Forward I say.

  • My advice:

    1) Adhere to the published standards for mark-up and styling. Forget about making the site look the same in any browser that has its own ideas about how to render them.
    2) Use transparent png files as needed without javascript fixes: support was part of the CSS 1 spec.
    3) Use as much CSS3 styling as you like as long as you allow for graceful degradation.
    4) Don’t use proprietary mark-up like conditional comments; instead, use object detection to display a polite message to users with outdated browsers that they should upgrade to enjoy the full experience.

    The *only* way the dev community is going to break out of the misery of writing the site twice just to support IE 6/7 is by taking the decision not to do so when we have that opportunity. This is one of those times.

  • “At some point, people with 8 bit screens, 640×480 resolutions and IE6 browsers should be abandoned. IMHO, it’s not that big a deal since they are used to whatever crappy web experience they are getting with their outdated tools.”
    ^dumbass

    The 640×480 device that was once the best you could get on a 58lbs bolted to the floor IBM PS2 is what you can get now on a Nokia Tablet weighing 15 ounces or less, these ‘inferior specs’ are like hand-me-downs” – The blackberry has limited Javascript, memory and browser support
    YET- has as much processing power as a $3,000 pc of yesteryear
    support them all, I say, each with functionality according to their limitations and medium.

    for instance, on keyboard-less devices, you can have view only interface, or have your ‘comment’ interface provide a simple “Opinion-response-menu” to make it easier on them BUT still allow participation

  • ummm… I apologize for the “dumbass” remark. It was introduced in error.

    (I was watching Faux News at the time and…)

Leave Your Own Comment