Proprietary web-coding ends here?

About 40% of my visitors (and not including me) to my blog agree: FireFox is better to browse. At least, it is used in 40% of the times people read here.
This leaves 60% of the readers using Internet Explorer (IE), where about a quarter is using ‘ye olde’ IE6 and more than half the amount of the IE-users is browsing with IE7.


While IE7 is finished about a year ago, the development of IE8 is nearing completion. For all of you who do not web-dev: IE sucks and is not standards-compliant. This is the case for IE5 through IE7, of which the latter is not neccessarily the worst as one of its goals was to better adhere to the web standards as defined by W3C (which it currently does not 😉 ).
A recent blogpost on the IE8 developers-blog has raised a lot of scepticism among webpage developers and html-coders as Microsoft intended to make a standards-compliance mode an option.
As IE8 is capable to pass the infamous ACID2-test, the intention was to make this behaviour not the standard behaviour of the browser, while the standard-rendering engine of IE8 had to be backwards compatible with the errors and bugs of the previous versions of IE (of which IE6 has the worst reputation).

Luckily, the so called meta-switch has been abandoned, and the developers have decided the backwards-compatibility modus is to be op-in, and the standards-compliance modus is the standard rendering engine of IE8.
The tech-talk put aside: with the new version of Internet Explorer on its way it seems as though IE an Fx will be rendering webpages nearly the same.
This is good for coders, as the quirks of a specific browser do not have to be taken into account when developing a web-page, so there’s only the need to maintain 1 version of the page. yay!