alt Hacker NewsYep. All HTTP/2 features are subsumed by HTTP/3 and all HTTP/2 deployments should be focusing their effort on moving to HTTP/3.
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.
Replies
chrisweekly • today at 5:07 PM
Hmm, I'd define that as "deprecated", not "obsolete". Many extant H2 deployments are stable and performant, and if they're eg fronted by an H3 CDN, the migration ROI might be questionable. /$.02
7bit • today at 5:19 PM
[dead]
HTTP/3 is fundamentally a different architecture than /2. To fully embrace it requires rethinking backend design significantly; just bumping a version number on HTTP without utilizing the intention of the spec is incorrect.
HTTP/1.x is not obsolete. It fills a very relevant request structure that most of the Internet still runs on.