3 ms·
They took Spdy and dropped priorities, settings and other ill-conceived parts from it and made compression and encryption optional. So they prioritized differe
by huggyface 14y ago
They took Spdy and dropped priorities, settings and other ill-conceived parts from it and made compression and encryption optional.
So they prioritized different things. That doesn't make it much better.
As an aside, where is the Microsoft reference implementation of Speed+Mobility? Where is their browser support for it? This, like so many Microsoft initiatives, seems primarily intended to delay and divert an initiative to make the web better.
- tedunangst 14y ago"just roll it out and make everyone do what we did" is precisely the mechanism that has saddled us with innumerable busted protocols and bizarre implementation artifacts.
- jamesaguilar 14y agoThen again, hard to argue that strategy is all bad. We have the internet as it is today, which while perhaps not ideal, is quite a thing.
- nl 14y agoYep! Any day now the beautifully designed X.25 protocol[1] will replace TCP, just like OSI[2] predicted. Rough Consensus and Working Code[3] built the internet, and it seems to work well enough to be useful. [1] http://en.wikipedia.org/wiki/X.25 http://en.wikipedia.org/wiki/X.25 [2] http://en.wikipedia.org/wiki/Open_Systems_Interconnection http://en.wikipedia.org/wiki/Open_Systems_Interconnection [3] http://en.wikipedia.org/wiki/Rough_consensus http://en.wikipedia.org/wiki/Rough_consensus
- tedunangst 14y agoYou appear to have reached a very different conclusion than I.
- huggyface 14y agoIt is also a way to essentially put your money where your mouth is, aligning interests and ensuring that you really believe what you're saying. Pushing out specs is a little too easy to simply delay others from doing anything. Further implementations can be credibly compared and considered. Many "HTML 5" features came via Google Gears, and would have taken a decade the traditional paper route.