Both slogans read the same — your code runs on demand, no server to manage. But one runs a full Node.js box in a single far-away data center, and the other runs a stripped-down V8 isolate a few milliseconds from your user. The difference between them is where they run and what they're allowed to do, and that difference decides which one belongs on your request path.
HTTP/3 didn't invent new headers or smarter routing — it kept HTTP exactly the same and swapped the pipe underneath. Instead of TCP plus TLS, it runs on QUIC over UDP, and that one change fixes head-of-line blocking, cuts the handshake to a single round trip, and lets a connection survive you walking from Wi-Fi to cellular.
There is a category of page load that takes zero milliseconds, because the browser already did the work before you clicked. The Speculation Rules API is how a page tells the browser which links to prefetch or fully prerender ahead of time — turning the next navigation into an instant swap. Here's how it works, and how not to set your users' bandwidth on fire doing it.
WebGL was OpenGL ES from the 1990s bolted into a browser tab — a giant global state machine that could only ever draw. WebGPU is a thin, modern layer over Vulkan, Metal, and Direct3D 12, and it does something WebGL never could: it runs general-purpose compute. That's why in-browser ML, physics, and data-crunching suddenly run at real speed, with no server round-trip.