3 ms·
> To get critical mass for HTTP/3 we'll need large server implementations (eg Cloudflare) and large client implementations (eg Chrome and Firefox) to build supp
by rumanator 7y ago
> To get critical mass for HTTP/3 we'll need large server implementations (eg Cloudflare) and large client implementations (eg Chrome and Firefox) to build support and drive adoption. Which is what is happening!
Isn't the critical path determined by the availability of web servers and client libraries? I get the importance of browsers, but I would guess that having HTTP/3 supported by projects such as Apache or nginx or curl is far more critical.
- steveklabnik 7y agoIt's a chicken and egg problem; without having clients, there's no reason for servers to support things, and without servers, there's no reason for clients to support things. It seems everyone recognizes this and so both clients and servers are getting implementations going to make sure this all goes smoothly.
- rumanator 7y agoNginx and Apache alone run about half of all active sites. That's pretty much the critical path to adoption. In fact, I'd argue that it would be impossible to adopt HTTP/3, or any other protocol, if those projects don't support it.
- steveklabnik 7y agoSure. I’m not saying that they aren’t valuable. I’m saying that they are, but clients are too.
- pdimitar 7y agoAre you guys working on a QUIC and HTTP/3 client/server in terms of future de-facto go-to crates for Rust? That would be amazing.
- steveklabnik 7y agoCloudflare has made quiche, but I can't personally say that it's the go-to; I just haven't had direct experience enough. We'll just see how it all shakes out.