Version Targeting Redux

Perhaps in response to the online backlash from the developer community about IE8's proposed method of version targeting, or, as Microsoft's own press release hints at, fear of more potential legal trouble in the EU, the guys behind Internet Explorer announced yesterday that, after thinking long and hard about their previous position on the matter, IE8's wholly embraced (then widely criticized and, ultimately, reluctantly accepted) version targeting system was going to adhere to standards mode by default.

Whatever the impetus for this about-face is, the only thing that matters is that Microsoft has finally started making good decisions about web standards support.

Instead of continuing to put the onus on developers to submit to IE's quirks, Microsoft has finally woken up to the fact that the standards are here to stay and that the only way for the web to progress is to stop pandering to incompetence. That may seem a little harsh, but it's the truth. The web has grown by leaps and bounds over an incredibly short period of time, and the innovations we've come to expect from the web can only continue if EVERYBODY works towards the same goal- an open, accessible web.

I can completely understand Microsoft's desire to support older sites. Given the size of their userbase and the number of legacy intranets that depend on IE6 quirks, it's impossible (and unacceptable) to expect them to completely drop support for those customers. On the other hand, it is equally unacceptable that standards-aware developers be forced to use outdated technologies and compromise what's possible simply for the sake of those legacy applications.

With the news that IE8 will now, thankfully, take the logical route of rendering in IE8 Standards mode by default, the web community as a whole can only benefit from it's release. The web will, hopefully, no longer be restricted by Microsoft's (again, understandable but incorrectly handled) coddling of legacy users. Those users now have two options: set their servers to trigger the appropriate rendering engine in IE8, or get their code compliant. The latter is obviously preferable and will hopefully see some significant play, but in reality, probably won't. Those developers that have grown used to being pandered to by Redmond will probably just choose the first option (the quickest and cheapest, so I can't really fault them). But, hey, that's OK. They don't need to update if they don't want to, as long as the rest of us no longer need to worry about Microsoft "favoring" incorrect websites.

So thank you, Microsoft, for stepping up and putting some support behind your (let's be honest, less-than-fulfilled) past pledges to support web standards. It is really, truly appreciated.