I would argue that uBlock Origin is a far more impactful technology than HTTP/3 for increasing website responsiveness and reducing load time in real-world usage.

I just learned about HTTP/3 a few days ago. In Belarus I am having problems opening any site that uses cloudflare (e.g. qbittorrent.org, openstreetmap.org) beginning just about the time russia started messing with youtube. The solution for now is to set network.http.http3.enable to false in Firefox.

Just seems like you have to go far off the beaten path to use it so far. Maybe your load balanced will do it for you, maybe you can bring in and use hyper/h3, but short of that you're back to assuming your own webserver with no frameworks. https://github.com/hyperium/h3

Node has been slowly working along towards QUIC support. I dunno where Go is. https://github.com/nodejs/node/pull/53256

I find it somewhat of a shame that dns-over-http3 seems to have killed dns-over-quic and dns-over-dtls.

In my own testing the benefit of going dns-over-http3 is that it finally brings dns-over-https down to speeds comparable to dns-over-tls.

I wonder what is left on the table by not going the simple route of having a "dedicated protocol" over udp (understand what I mean, not what im saying).

I miss HTTP/1.1. Yeah it’s slow, but it’s dead simple to implement. HTTP/2/3 are way more bloated and complex.