HTTP/3 is everywhere but nowhere
httptoolkit.com
HTTP/3 is everywhere but nowhere
1–10 of 504 posts
Re: HTTP/3 is everywhere but nowhere
#2 > At the same time, neither QUIC nor HTTP/3 are included in the standard libraries of any major languages including Node.js, Go, Rust, Python or Ruby.
Support for Windows, Linux[2], and Mac[3] (the latter two with some caveats).
Overall, I think for most dev teams that are not building networking focused products/platforms, HTTP/3 is probably way down the stack of optimizations and things that they want to think about, especially if the libraries available have edge cases and are too early for production. Who wants to debug issues with low-level protocol implementations when there are features to ship, releases to stabilize, and defects to fix?
[0] https://learn.microsoft.com/en-us/dotnet/fundamentals/networ...
[1] https://github.com/microsoft/msquic
[2] https://learn.microsoft.com/en-us/dotnet/fundamentals/networ...
[3] https://learn.microsoft.com/en-us/dotnet/fundamentals/networ...
Re: HTTP/3 is everywhere but nowhere
#3For bidirectional 2 TCP sockets and HTTP/1.1 Comet-Stream works fine.
Fighting HTTP/1.1 for money is going to fail unless you invent something fundamentally better.
Re: HTTP/3 is everywhere but nowhere
#4as an indie web master, some percentage improvement on ttfb brings zero benefit to me and my users, but requiring or recommending it to users only help big tech.
Re: HTTP/3 is everywhere but nowhere
#5How much does http/3 help for server to server traffic? Seems like larger websites can use a CDN or load balancer to do termination and then use http 1.1 to the back end. Is that good enough with large pipes and a high number of connections?
Re: HTTP/3 is everywhere but nowhere
#6My recent projects in C++ are just using cURL, but given some of the versions of cURL I have to support are 10 years old it isn't being turned on anytime soon.
Even the latest deployments on Rocky 9 are using a 4 year old version of cURL
When you're writing libraries distributed as binaries for other teams you can't just statically link whatever you want willy nilly.
Re: HTTP/3 is everywhere but nowhere
#7My recent projects in C++ are just using cURL, but given some of the versions of cURL I have to support are 10 years old it isn't being turned on anytime soon. Even the latest deployments on Rocky 9 are using a 4 year old version of cURL When you're writing libraries distributed as binaries for other teams you can't just statically link whatever you want willy nilly.
What prevents you from using a package manager linking statically with a recent libcurl ?
Re: HTTP/3 is everywhere but nowhere
#8How much does http/3 help for server to server traffic? Seems like larger websites can use a CDN or load balancer to do termination and then use http 1.1 to the back end. Is that good enough with large pipes and a high number of connections?
I subscribe for that
Re: HTTP/3 is everywhere but nowhere
#9It's pretty glaring that nginx still doesn't have production-ready HTTP3 support despite being a semi-commercial product backed by a multi billion dollar corporation. F5 is asleep at the wheel.
Re: HTTP/3 is everywhere but nowhere
#10Every single project mentioned in the article is to some extent either open source and/or community driven.
So nobody considered HTTP/3 interesting enough to rush and add support for it very quickly. It'll get there, but fast? I don't think so, see IPv6.
Also, nobody considered HTTP/3 worth enough of paying for maintainers to add support for it.