3 ms·

The number of requests that Googles homepage does in order to load has _nothing at all_ to do with It has a lot to do with the desire to work around limits on

• dagenix 8y ago
  Google has spent at least 6 years (and counting) working on SPDY / HTTP2 / QUIC on design, experimentation, implementation, and specification tasks. This is low-level, complex work that requires a combination of experience and talent. This is expensive work - and there was never any guarantee it would pan out. I think it's unreasonable to assert, without evidence, that they did all that just because parts of their organization are incompetent and they refuse to fix it or that the problems they are trying to address have some sort of trivial solution. It's also pretty unreasonable to point at www.google.com and say that it makes too many requests and it could be trivially fixed to use fewer. But, let's assume that the problem you identify actually is the case: Google is a huge, cash rich organization - if they can't figure out how to enact the change you suggest, how could any other organization? And if HTTP/2 and QUIC (HTTP3) solve this problem for Google, and since they are making it an open standard, also for other organizations, why is that a bad thing?