Hacker News Reader

Comment by kristianp | Hacker News Reader

It looks like the usual Microsoft 'embrace and extend' strategy.

It would be if they weren't working with the IETF to have their additions become HTTP 2.0.

There's no difference between Google extending SSL, implementing that in their browser and servers and then submitting it to the IETF and Microsoft adding additional features to SPDY and submitting those too for consideration.

Only when their changes get turned down, but then still appear in IE in such a way that it only supports the changed SPDY but not the original any more, only then I would have to agree with you.

At the moment it doesn't look like that is the case though.

Microsoft has worked with standards bodies for CIFS, Kerberos and LDAP, the whole pile of web standards (and their .docx thing, but this one is a joke). It doesn't mean you can interoperate with them, because they have introduced involved bugs and matching workarounds, then enshrined them for decades by never breaking compatibility. SPDY can avoid this because it already has diverse implementations in the wild, but if Microsoft acquires credibility for mobile extensions to SPDY, they'll push a half-broken implementation to carriers and gain a competitive advantage on smartphones.

And ECMAScript which they held back for a year or more and garnering the wrath of Brendan Eich not too long ago.

> It would be if they weren't working with the IETF

Like they "worked" with ISO on OOXML?

Sorry. They have to earn back some trust after what they did there.

Reply on news.ycombinator.com