The problem is that it isn't a choice of MSIE6/7/8 or MSIE9, it is MSIE6/7/8 AND 9.
While it hasn't always been that way, at least lately (since MSIE7 and 8) Microsoft has been working hard to get rid of the older versions as well and the newer versions (while certainly not perfect) most definitly improves on the shitty standards support found in MSIE 6.
In MS's latest technet newsletter there is even a link to a paper on virtualizing older versions of MSIE so you can upgrade to something modern while retaining compatibility with older legacy apps requiring MSIE 6. [1]
So while MS can be blamed for producing MSIE 6, the blame for that MSIE is still around lies entirely in corporate IT and them not using the options they most definitely have for getting rid of it for mainstream use.
While it hasn't always been that way, at least lately (since MSIE7 and 8) Microsoft has been working hard to get rid of the older versions as well and the newer versions (while certainly not perfect) most definitly improves on the shitty standards support found in MSIE 6.
In MS's latest technet newsletter there is even a link to a paper on virtualizing older versions of MSIE so you can upgrade to something modern while retaining compatibility with older legacy apps requiring MSIE 6. [1]
So while MS can be blamed for producing MSIE 6, the blame for that MSIE is still around lies entirely in corporate IT and them not using the options they most definitely have for getting rid of it for mainstream use.
[1] http://www.dabcc.com/documentlibrary/file/Solutions_for_Virt...