I would been pleased to see this project named something else, maybe “httpx-ng” or “httpy” as I immediately link “http*2” with the obsolete http/2 protocol and not the httpx project.
(FWIW I agree w/ your objection to the "httpx2" name.)
HTTP/2 is full of growing pains and fiddly kernel config for it to perform better than even HTTP/1.1.
Moving these dependencies into userland was the path that HTTP/3 took and it has proven itself through CDN and browser adoption for years now.
I’d go as far as to say that we need to reevaluate the event loops in nginx and elsewhere to assume UDP and HTTP/3 framing instead of TCP. There are gains to be had.
The h3 juice is worth the squeeze. 0rtt TLS, BBR, HPACK, etc. You can roughly achieve this with a carefully configured h2 deployment across multiple layers and packages or just move to h3 and let the app layer handle it all. We baked all of the best practices into h3, the world just needs to move on.
HTTP/1.x is not obsolete. It fills a very relevant request structure that most of the Internet still runs on.