I submitted a reply to A Browser for All Windows Customers: it’s about and, not or - IEBlog - Site Home - MSDN Blogs, but it was "moderated" away. Apparently, Microsoft only approves comments by sycophants and strawmen.
Here is the comment, for anyone curious:
So foot-dragging is a feature?
That just seems like a rationalization for not supporting standards in the coming years (HTML5 inputs, e.g.), and being the holdout on auto-upgrades, the only hope many web developers had of seeing reasonable standards support (as opposed to kludgy workarounds) before the end of their career.
Hopefully Chrome Frame will make some inroads for the sake of developers, upon whose back the "great" IE experience comes. (Can someone from Microsoft supply, from their vast compatibility stats, how many top Internet sites are likely to use hardware rendering vs. how many take date inputs?)
Don't expect a lot of sympathy just because the job is impossibly big. Microsoft used anti-competitive practices to make IE the default browser, and has now found itself in the position of having to support up to FOUR rendering engines per browser per OS per service pack. And it's only going to grow, this thankless position of "infrastructure". More rendering engines will accumulate geometrically year after year (in a product that doesn't even show a profit) until Microsoft just cannot sustain any more and has to make some tough decisions about backward compatibility.
I think the track record shows that this realization often comes quite late in Redmond.