Hacker News Reader

Comment by CJefferson | Hacker News Reader

Well, in 2003 (14 years after the release of HTTP 1.1), Twitter considered it acceptable to remove HTTP 1.0 from their API access (You can still access the website itself fine over 1.0).

I expect to see 1.0, 1.1 and 2.0 continue to live on basically forever.

Of course, the interesting question will be how fast will the majority of users, and servers, be running 2.0?

View on HN

I think you mean 2013.

Thanks, yes :)

The majority of desktop browsers in use already support HTTP/2. Things are going to be slower on mobile, obviously. Thankfully it isn't all or nothing -- your server side load balancer / SSL termination supports HTTP/1, 1.1, and 2.0, and provides the client the experience they can support.

Why slower on mobile? The upgrade cycle on phones is much shorter than PCs, so even if you never put new software on a phone, you'll get an HTTP/2 enabled browser quickly.

On the software side, Google-derived Android comes with Chrome by default, which already support SPDY and HTTP/2 support is imminent. Safari on iOS 8 supports SPDY, ditto on HTTP/2 coming soon. Both those software updates can be done instantly (via Google Play Services) or within a year (yearly iOS updates).

So I'd think mobile support is coming very quickly.

> Why slower on mobile? The upgrade cycle on phones is much shorter than PCs

Disagree. Phone manufacturers adopt Android versions slowly, especially at the low end, and on PC both Firefox and Chrome update themselves.

It's not about the upgrade cycle of the hardware, but the software. Browsers stay up to date automatically, even on 10 year old PCs. Phones are often abandoned by their providers and run old versions of the OS that are not automatically updated to the latest browser tech.

Reply on news.ycombinator.com