4 ms·
I visited a few common sites and they seem to use HTTP/2. I'm not sure the point of arguing it's not fundamental, a cursory glance shows HTTP/1 is bottlenecked
by mrmuagi 3y ago
I visited a few common sites and they seem to use HTTP/2. I'm not sure the point of arguing it's not fundamental, a cursory glance shows HTTP/1 is bottlenecked by not being able to use the same TCP connection to serve multiple resources (something HTTP/2 fixes)? Is there ire against HTTP/2 adoption, and for what reasons?
- jakub_g 3y agoI'm not an area expert, but common issues raised over the years: - HTTP/2 as implemented by browsers requires HTTPS, and some people don't like HTTPS. - HTTP/2 was "designed by a committee" and has: a lot of features and complexity; most of those features were never implemented by most of the servers/clients; most of those advanced features that were implemented were very naive "checkbox implementations" and/or buggy [0]; some were implemented and then turned out to be more harmful than useful, and got dropped (HTTP/2 push in browsers [1]) etc. [0] https://github.com/andydavies/http2-prioritization-issues https://github.com/andydavies/http2-prioritization-issues [1] https://developer.chrome.com/blog/removing-push https://developer.chrome.com/blog/removing-push
- fzzzy 3y agohttp 1.1 connections can be reused, including with pipelining, and it can open multiple sockets to make requests in parallel. http 2 allows out of order responses on one socket. is it worth the complexity? http 1.1 is over 20 years old and battle tested.
- yencabulator 3y agoClients stopped using HTTP/1.1 pipelining because it just didn't work well enough. https://en.wikipedia.org/wiki/HTTP_pipelining#Implementation_in_web_browsers https://en.wikipedia.org/wiki/HTTP_pipelining#Implementation...
- s3p 3y agoEvery tech company uses HTTP/2. I'm confused as to what the comment before yours is trying to say, it doesn't seem to be supported by any facts.