The straw that broke IE6's back...

[biznuge]

Lo all,

I just found myself laughing maniacally when I saw what IE6 did to my latest jquery enhanced semantic drop down menu, and have thus decided that it's not worth my time or effort supporting this absolute piece of **** any more, and that there are far more important things in life than trying to hack my own products to fit into a product that Microsoft didn't even build right the first time.

Seriiously though. the IE6 version differed so dramatically from IE7/FF/Safari/Chrome/Opera that I see no point in providing any kind of backward compatibiility.


Sod it...

Does anyone out there still support <IE7 anyway. thoughts would be appreciated....



haha. srsly though. just pure Haw.... :fight:

[NeoDreamer]

It really depends on who your audience is. If it's a relatively high-tech website, then most of your audience won't use old browsers. If you're making a site meant to be used by everyone, then you better support the 30% or so people still using IE6. You can't force them to upgrade. If they're too stupid to use IE6, they're too stupid to follow your instructions asking them to upgrade to FF or Safari.

My golden rule is to just make sure that the site is functional in IE6. It doesn't have to look good, but at least have the buttons do what they're meant to do.

[biznuge]

yeah. it barely accomodates the "functional" criteria. links are clickable, and you can nav the site as normal, but it just looks amazingly bad.

ho hum!

[Swooter]

Internet Explorer 6 is 8 years old. Even YouTube doesn't support it anymore.

[simplistik]

Screw IE6 people will continue to use it as long as you support it. I refuse to develop for IE6 anymore. I especially hate trying to debug JS in IE6 because it's so terrible at it.

[TheCanadian]

I'd still be using IE6 if I didn't get a new computer.

[jwilliam]

I work for a fairly large company and a little over 20% of our traffic is from IE 6 users (within the last 30 days). I couldn't believe that when I first checked it a few days ago. I don't support IE 6 in my own projects, but at work I have to. Maybe a few more months of Windows 7 will be the final nail in the coffin.

[biznuge]

yeah. ours is still in that range from our stats package at work, so we still have to keep supporting the piece of crap. Think that may be why I'm still habitually doing it for my freelance stuff, but...

I shall NO MORE!!!

[TheCanadian]

Yeah alienating 1/5 of your user base is a better option.

[biznuge]

yeah...

but...

well...

I just can't be arsed any more... if the truth be told...

haha!

[simplistik]

the problem is you can't do progressive web development by still trying to get IE6 to work all the time. what i do is give my clients the knowledge about IE6 and then give them a rough demographic, and then explain the cons. i charge x amount for regular work and then y for IE6 support. generally tho this only is applicable for sites that have hardcore JS on them, because in general markup is cake to get working on all browsers.

[biznuge]

That's pretty much what I had in mind to be honest. charge flat rate for actual "web dev" and then add on pro rata as clients see fit to waste their time with supporting evil legacy.

Thanks for the responses everyone. Nice to know I'm not even slightly alone in this.

[TheCanadian]

Yeah alienating your clients is a better option.