What you say is probably true, but it is severely broken. Let me give an example.
If you talk to users, very few will care that IE doesn't support key web standards that every other major browser does, because everyone is going to make things work on IE anyways. However if you talk to users, lots care that it is easy to develop rich web content. However the users don't have the perspective to understand that standards support will get them better web content.
Therefore IE decides that better standards support is not a priority. And doesn't implement it.
Conversely if IE did decide to implement better standards support, everyone would be better off.
However Microsoft wouldn't get much credit for it, because it wouldn't be obvious to users how important Microsoft's role was in making things better. And developers would say, "Finally!" But then curse Microsoft for years anyways because it takes that long to get the old, broken, browsers off of the market.
The result? IE is crap. And will remain crap. Indefinitely. And Microsoft is convinced that this is not a problem. (And for them it isn't - except for the also invisible problem that they have developed hiring problems in part because many good developers can't stand that attitude.)
I think you're being unfair. You act as though they aren't implementing any standards instead of just the ones that make a difference. At the end of the day, websockets is a mess and shouldn't (and isn't) be enabled in any web browser yet. But a whole bunch of other things are. Check the compatibility list: http://msdn.microsoft.com/en-us/ie/ff468705.aspx. They actually have pretty solid support for most of the upcoming standards and are playing a significant role in the W3C process itself.
If you talk to users, very few will care that IE doesn't support key web standards that every other major browser does, because everyone is going to make things work on IE anyways. However if you talk to users, lots care that it is easy to develop rich web content. However the users don't have the perspective to understand that standards support will get them better web content.
Therefore IE decides that better standards support is not a priority. And doesn't implement it.
Conversely if IE did decide to implement better standards support, everyone would be better off.
However Microsoft wouldn't get much credit for it, because it wouldn't be obvious to users how important Microsoft's role was in making things better. And developers would say, "Finally!" But then curse Microsoft for years anyways because it takes that long to get the old, broken, browsers off of the market.
The result? IE is crap. And will remain crap. Indefinitely. And Microsoft is convinced that this is not a problem. (And for them it isn't - except for the also invisible problem that they have developed hiring problems in part because many good developers can't stand that attitude.)