Precisely - and just like that one line of code is enough to spawn a HTTP server, a different line of code could be enough to spawn a HTTPS server. It's a matt

Precisely - and just like that one line of code is enough to spawn a HTTP server, a different line of code could be enough to spawn a HTTPS server. It's a matter of improving the tooling. No one is advocating to disable HTTP today, what browser vendors are trying to do is get the ecosystem to a point where that's possible without a significant increase in cost for site operators. Similarly, HTTP/2 has been tuned specifically for (typically high-latency, low-bandwidth) mobile connections and is practically (at least) indistinguishable from the speed of (optimized) HTTP. This is only going to improve with things like Zero-RTT handshakes coming with TLS 1.3.