News for hackers. Stuff that matters.
Re:HTTP/2.0 – Please admit defeat by bostik on Monday May 26, 2014 @05:22AM (#7799165)
I am not sure how well that applies to a protocol that is supposed to be codified in every single browser, web server and utility library in the world. The iteration cycle will be slow, and improvements can not happen overnight.

Now, if the name was something like HTTP/1.8-alpha it might be a different thing. At least then it wouldn't carry the label of the "next big thing for everyone". It's sad, but names (and branding) do matter. Forcing a known-broken implementation upon the world is not exactly good engineering.

Re:HTTP/2.0 – Please admit defeat by twic on Monday May 26, 2014 @06:42AM (#7799283)
WebSockets went through a series of iteration cycles like this. It wasn't entirely smooth sailing, but it seems to have worked out.
Re:HTTP/2.0 – Please admit defeat by wmf on Monday May 26, 2014 @01:07PM (#7800569)
Google can iterate on SPDY and QUIC by just releasing new versions of Chrome, which is where all the knowledge behind HTTP 2.0 came from.
Re:HTTP/2.0 – Please admit defeat by dsl on Monday May 26, 2014 @03:41PM (#7801232)
This is often overlooked as the single biggest failing of SPDY... its a protocol designed to work well for Google, which operates completely differently from every other web property.

Google in-houses everything so a single fast multiplexed connection to a single server makes sense. Every other website has external content, ads, like buttons, etc. and you end up having to spin up 30-40 independent SPDY connections, eliminating all benefit.