Really? I've been pretty happy with IE9, generally 98% of my code works perfectly, it's just a matter of drop shadows, rounded corners, etc that don't work. I honestly want to know what breaks so horribly that it's like coding a site twice.
My memories of IE6 make IE9 seem like a completely different browser. It is somewhat, since they rewrote their rendering engine to fully support CSS 2.1 in IE8.
The one promising thing is that the IE development team now seems to be really intent on supporting open standards and being compatible, and they're catching up faster than they used to. They should reach parity within another major release or three.
Can you elaborate? What IE11-specific features do current web site require? I'd like to find out what I've been neglecting...
Agreed, thank you! I'm pretty close to launching a web app I've been developing over the past 6 months or so; I've decided not to support any version of IE.
I made that decision in part b/c of the feature set it needs to support, but also due to principle - I don't believe Microsoft has ever been as passionate about the web as it's competitors. The browser apathy represented in IE 6 - 8 supplements that, and we still see the same in recent versions. For example, IE 9 lacking support for local databases, ES5 strict, remaining on long-term release cycles, etc. So if we want better, we have to vote for it, by choosing to drop support for the lesser browsers that exist in the ecosystem.
Other ways to move the web forward: stop supporting Internet Explorer altogether. That browser needs to stop being coddled and forced to get with the times. The difference between Webkit and Gecko rendering is almost a non issue but when you start having to support Trident then it's almost like having to code a site twice. Let's just stop supporting it and either let that thing die or force it to keep up. Version 9 and 10 are steps in the right direction but it can do better.
That said, we can't always drop IE support. Very high traffic, corporate, and intranet sites will still need to have support for IE for some time but all in all, lets drop it when it makes sense. Personal sites and even some business sites can work. I personally don't do anything to specifically support IE on my own business' website and it hasn't hurt me a bit. Let's take a risk here and there and drop IE support and move forward.
Moving forward is about more than just code though. It's also about user experience. A site with code that's 100% valid but is hard to use or uses distracting elements like gratuitous animations isn't moving forward. It's just building a site that looks like its from the 90's except with modern, valid code. That's lame.