2 ms·
> That is a ridiculous statement with absolutely no evidence to back it up. I’d hate to bring it up but here goes: SPDY was designed specifically to load the G
by josteink 8y ago
> That is a ridiculous statement with absolutely no evidence to back it up.
I’d hate to bring it up but here goes: SPDY was designed specifically to load the Google homepage quickly on typical American DSL MTU configuration, even with all that JavaScript tracking enabled.
Turned on it’s head: SPDY was designed to make google’s wide tracking of end-users impact page-load times as little impact as possible, to avoid it being a cause of end-user dissatisfaction.
SPDY was extremely tailored to a very niche need which first and foremost serves Google.
- dagenix 8y agoThe thread here is about HTTP3 - ie, HTTP2 over QUIC. HTTP3 has features that are going to benefit high latency, high loss connections a lot. Things such as speeding TLS negotiation, and only having to do it for one connection; better handling of packet loss; forward error correction (if it works). I see you don't cite any evidence that SPDY was miopically designed for American DSL connections, but regardless of that, HTTP3 is going to benefit a wife range of connection types.