And interop is quite valuable for web users. But for the so-called "tech" companies and CDN service providers authoring the HTTP/2 RFCs, maybe not so much.
Who receives the primary benefit of HTTP/2. Certainly not web users. Perhaps they get some small secondary benefits.
What does not make any sense to me is why past/present Googlers and other HTTP/2 proponents voting and replying on HN are offended by someone who likes using HTTP/1.1. For pipelining. The (non-browser) interop is much better than HTTP/2. That is, using 1.1, I can pipeline HTTP to/from almost every httpd on the internet, using a vast array of TCP clients written over a long period. If I want to use HTTP/2/, the number of libraries and clients is much smaller and all are recent. Further, AFAIK these clients cannot pipeline the way 1.1 does, retrieving many files from same host sequentially over single TCP connection, in the order they were requested, with HTTP headers. Google existed when RFC2616 came out. If it is so flawed then why not try to change it then. HTTP/2 is flawed for what Google and other so-called "tech" companies want to do, always with a browser or mobile OS they control, not necessarily what web users want to do, with whatever clients web users choose, 100% of the time. We've seen the stuff so-called "tech" companies get up to and it usually involves surveillance to support commerce. HTTP/2 isn't going to solve or alleviate any of those ills.
To keep the Wall Street analysts happy, Google will not be adding to their browser, inspiring and backing standards that translate to less profit for Google. If a new standard decreases the amount of data collection or tracking, that's less profit for Google. HTTP/2 is not such a standard.
And interop is quite valuable for web users. But for the so-called "tech" companies and CDN service providers authoring the HTTP/2 RFCs, maybe not so much. Who receives the primary benefit of HTTP/2. Certainly not web users. Perhaps they get some small secondary benefits.
What does not make any sense to me is why past/present Googlers and other HTTP/2 proponents voting and replying on HN are offended by someone who likes using HTTP/1.1. For pipelining. The (non-browser) interop is much better than HTTP/2. That is, using 1.1, I can pipeline HTTP to/from almost every httpd on the internet, using a vast array of TCP clients written over a long period. If I want to use HTTP/2/, the number of libraries and clients is much smaller and all are recent. Further, AFAIK these clients cannot pipeline the way 1.1 does, retrieving many files from same host sequentially over single TCP connection, in the order they were requested, with HTTP headers. Google existed when RFC2616 came out. If it is so flawed then why not try to change it then. HTTP/2 is flawed for what Google and other so-called "tech" companies want to do, always with a browser or mobile OS they control, not necessarily what web users want to do, with whatever clients web users choose, 100% of the time. We've seen the stuff so-called "tech" companies get up to and it usually involves surveillance to support commerce. HTTP/2 isn't going to solve or alleviate any of those ills. To keep the Wall Street analysts happy, Google will not be adding to their browser, inspiring and backing standards that translate to less profit for Google. If a new standard decreases the amount of data collection or tracking, that's less profit for Google. HTTP/2 is not such a standard.