Google Chrome to ditch SPDY — implementing HTTP/2
Brian Fagioli / BetaNews :
Context & Ripple Effects
Chrome's move retires Google's own experiment: SPDY was the prototype protocol Google built to speed up the web, and HTTP/2 is the IETF standard that grew out of it. With Chrome switching to the standard, the browser that invented the approach is also the first big player to declare the prototype dead.
The timing matters because the ecosystem had just started standardizing around it — months later Cloudflare rolled out HTTP/2 to all its users to force adoption, and followed with HTTP/2 Server Push, which it expected would cut load times by up to 15% across its network.
First-order effects
- Site operators still serving content over SPDY to Chrome users lose those performance gains once the browser drops support, pushing them to upgrade servers to HTTP/2 or fall back to plain HTTP/1.1.
- Server and proxy vendors now have a hard deadline signal: the largest browser by market share will only speak the standardized protocol, so SPDY implementations become legacy code.
Second-order effects
- CDNs and hosting providers compete on who enables HTTP/2 first — Cloudflare's all-user rollout shows infrastructure players treating protocol support as a differentiator to spur adoption among their customers.
- Web performance tooling and load-testing vendors must add HTTP/2 multiplexing behavior to their products, since connection-level assumptions from the SPDY era no longer match production traffic.
Third-order effects
- Browser vendors deprecating their own experiments once standards land establishes a template Google reuses elsewhere — the same forced-migration playbook later appears in its plan to distrust Symantec-issued certificates and mark plain HTTP as not secure, pairing protocol upgrades with security pressure.
- If the pattern holds, each HTTP generation gets a short shelf life: the corpus already shows Chrome and Firefox shipping TLS 1.3 and then HTTP/3, meaning sites face a continuous upgrade treadmill rather than a one-time migration.
The trend: Web transport protocols are consolidating from vendor experiments into IETF standards, with browser market share acting as the forcing function that retires each predecessor.