For IE9 we really focused on what customers, partners and developers told us mattered most, their sites. Developers wanted the ability to create richer and more immersive experiences on the web, and so we invested in fully HW accelerating HTML5 through Windows.
* Why no Websockets support?
We started by building a tool to look at the top 7000 sites and what web APIs they used. In IE9, we set out to support the standards that showed up among those sites. We also spoke to developers and partners to understand what they were going do in the future and what they couldn't do today
... every answer is like this.
For IE9 we really focused on what customers, partners and developers told us mattered most, their sites. Developers wanted the ability to create richer and more immersive experiences on the web, and so we invested in fully HW accelerating HTML5 through Windows.
Dev translation: we actually tested this. People didn't care enough about built-in spellcheck.
We started by building a tool to look at the top 7000 sites and what web APIs they used. In IE9, we set out to support the standards that showed up among those sites. We also spoke to developers and partners to understand what they were going do in the future and what they couldn't do today
I don't even have anything to add to this. They looked at who's using websockets and the standard. No one is using it. In fact, I don't see why IE is getting a bad rap for this -- none of the browsers currently have websockets enabled while the standard is being fixed. The rest of their comment is marketing-translated: "We do care about standards though, which is why we implemented the more common ones."
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.)
What I intended to communicate was that the incompetence applies to Microsoft as a whole. There's plenty of brilliant and competent individuals who work at Microsoft.
>>Does it work on my ubuntu laptop?
Dear iamnotobama - You may be surprised to hear that it actually does work on your laptop. It's a three-step process: 1.Install Windows 7 2.Install IE9, and 3.Enjoy the Beauty of the Web. ☺