4 ms·

Keep in mind that the HTTP/2 standardization process really started from SPDY [1]. Before HTTP/2 the standard hadn't changed significantly in _decades_ due to l

Keep in mind that the HTTP/2 standardization process really started from SPDY [1]. Before HTTP/2 the standard hadn't changed significantly in _decades_ due to lack of industry consensus and actual data. Google then used its unique position as a) massive web server and b) massive web browser to perform real-world protocol experiments that _nobody_ else could possibly do. SPDY came out of that (really cool!) work, and had some great benefits, and the working group started with the spec and worked to evolve it. The server-push originally comes from SPDY, and as I recall it seemed an obviously useful optimization at the time. It's a bit ironic that the same company that introduced it is now saying "we never really found a use for it". Disclaimer: I was employed by Google and on the HTTP/2 working group at the time. 1: https://www.chromium.org/spdy/ https://www.chromium.org/spdy/

LtWorf 4y ago
I'm not convinced that not changing a standard that is already quite flexible is a bad thing.
chrsig 4y ago
That's kind of arguing against yourself though. here's a more cynical take: - "only google can do these huge experiments, and we've blessed the world by sharing our discoveries, so we can have confidence that our proposals are validated with real world experience." - "That thing we standardized and got a bunch of other people to implement? yeah, i know we said it was really useful, but we meant it seemed really useful. We actually never found a use for it." can't have it both ways
- inopinatus 4y ago
  What it means is that the Google mindset of introducing and later killing off whatever services they feel like, extends to how they view the standards process, viz. that it’s theirs to tinker and butcher as well, and coupled to that the implicit belief that their implementation of the web is the reference implementation, and the rest of us simply subordinate to Google’s commercial preferences. Other vendors do this too - the fundamental conceit at play is as old as the tech sector - but that doesn’t make it any less arrogant or reprehensible behaviour. With that understanding, the process note above from an ex-Google employee amounts to a description of wilful abuse of market power.
- uluyol 4y ago
  So people aren't allowed to make mistakes? HTTP/2 was morphed by so many other entities besides Google and offers a host of benefits. Having one useless feature is hardly worth complaining about.
- pas 4y ago
  The top 100 websites are all big enough to experiment. Only Google cared enough to push for new shiny and fancy standards though.

LtWorf 4y ago

I'm not convinced that not changing a standard that is already quite flexible is a bad thing.

chrsig 4y ago

That's kind of arguing against yourself though. here's a more cynical take: - "only google can do these huge experiments, and we've blessed the world by sharing our discoveries, so we can have confidence that our proposals are validated with real world experience." - "That thing we standardized and got a bunch of other people to implement? yeah, i know we said it was really useful, but we meant it seemed really useful. We actually never found a use for it." can't have it both ways

inopinatus 4y ago
What it means is that the Google mindset of introducing and later killing off whatever services they feel like, extends to how they view the standards process, viz. that it’s theirs to tinker and butcher as well, and coupled to that the implicit belief that their implementation of the web is the reference implementation, and the rest of us simply subordinate to Google’s commercial preferences. Other vendors do this too - the fundamental conceit at play is as old as the tech sector - but that doesn’t make it any less arrogant or reprehensible behaviour. With that understanding, the process note above from an ex-Google employee amounts to a description of wilful abuse of market power.
uluyol 4y ago
So people aren't allowed to make mistakes? HTTP/2 was morphed by so many other entities besides Google and offers a host of benefits. Having one useless feature is hardly worth complaining about.
pas 4y ago
The top 100 websites are all big enough to experiment. Only Google cared enough to push for new shiny and fancy standards though.