Hacker News new | ask | show | jobs
by dstein 5668 days ago
I didn't say MS was "out to get the users", I just mean that every response Microsoft has to perfectly reasonable questions like "why don't you support [insert standard here]?" has the same patronizing tone like "we've listened to our customers and delivered a product that they are satisfied with".
1 comments
Locke1689 5668 days ago
Example? They may be skirting around saying something straight out for legal reasons (either proprietary or getting sued by a competitor).
link
dstein 5668 days ago
* Would it have killed you to have included a built-in spellchecker?

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.

link
Locke1689 5667 days ago
First, yes, it's in "professional speak." Given that some people from marketing are overseeing this, I would just expect that. The answers, however, don't strike me as condescending.

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."

link