12 ms·
According to the shills employed by or rooting for Google, here on HN and elsewhere on the internet, it's not silly: It is paramount. See, it allows the reques
by josteink 13y ago
According to the shills employed by or rooting for Google, here on HN and elsewhere on the internet, it's not silly: It is paramount.
See, it allows the request for www.google.com, including all of Google's tracking cookies, to fit inside one TCP-frame, causing a 5ms improvement in load time, and Google has evidence that this means they make more money.
Never mind the open, exploratory nature of the internet and how text-based protocols was what made the internet into what it is today. We're going to throw away all that which the internet has taught us about that because Google says we should.
This thing is fucked up beyond belief.
Edit: found a link to the IETF discussion about this:
http://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/0254.html http://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/...
It admits in plain sight that the only thing they care about with HTTP 2.0 is solving Google's massive-scale issues at the cost of everyone else:
> I finally admitted it was a dead end. At the moment the
challenges consist in feeding requests as fast as possible over high latency connections and processing them as fast as possible on load balancers
A good, open, self-documenting protocol didn't suit Google, so let's throw it away. It's a "dead end", after all.
Jesus christ these people need a bitch-slapping.
More emails on the subject can be found here:
http://www.w3.org/Search/Mail/Public/search?keywords=&hdr-1-name=subject&hdr-1-query=The+use+of+binary+data+in+any+part+of+HTTP+2.0+is+not+good&index-grp=Public_FULL&index-type=t&type-index=ietf-http-wg http://www.w3.org/Search/Mail/Public/search?keywords=&hdr-1-...