Found this interesting read over at ExpressionEngine.com and their forums. It’s about legacy browsers and how to compensate for the time it takes to develop sites for them.
Working with Legacy Browsers and Reduced Functionality
I also had my own little say in the argument.
I don’t fully agree with you, after reading the whole post (a very interesting read, nonetheless). Giving legacy users less functionality just because they are using an old browser (which could be due to lower privileges) just does not sound right in my ears. If there was such a thing as “browser racism” I believe it would fall into that category.
Fixing IE-bugs is annoying, but in the end it does almost always pay off. The perfect site is a site where you (as a developer) avoid building two different sites (one legacy and one regular). The perfect site is a site where all features are available to all users, regardless of browser or operating system.
In my opinion, of course =) !
After some more argumenting:
I think the difference between “less features for old browsers” and “more features for newer browsers” is very much the same thing. It all narrows down to not giving older browsers better goods because of either laziness or lack of time. Most often, also, removing the bells and whistles is the same as removing a good reason to like a certain site.
I just want to say that I would rather develop a site thoroughly and add features that risk bugging out in a step-by-step manner, making sure everything works in the end. It is a lot of work, but it is rewarding!
Agreed, but when developing smart features for say, an e-shop website, and not sharing these with IE users will leave them frustrated.

Svenska
Latest Comments in the Blog