h3

There's probably good advantages to a well tuned more bespoke multiplexing protocol toolkit… But it sure makes me crazy crazy sad that QUIC and HTTP3 are still rarefied technologies with little mainstream adoption. The hyperscalers all seem to have a library or two they've made… https://github.com/mmmarcos/awesome-quic?tab=readme-ov-file#... …but there's still no mainstream http3 that works well with a http framework of any kind that one can just use. Hyper's h3 kicks along slowly. Node.js has been beleaguered by openssl's endless beating around the bush reinventing how they want to do quic, ignoring input. But that's finally starting to move. https://github.com/hyperium/h3 https://github.com/nodejs/node/issues/57281 Muxio was able to define itself & an inpl pretty fast, and performance & usability are probably both medium or high. That e

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

To be determined. We're hoping to contribute and use what's going to come out of hyper's h3 efforts (we use Rust for our reverse-proxy). There's not much there yet though: https://github.com/hyperium/h3 We're not in a huge hurry to support QUIC / H3 given its current adoption. However, our users' apps will be able to support it once UDP is fully launched, if they want to.