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.
Seems like the major gripe is over my usage of the word “obsolete” instead of “deprecated”. We could all be flipping switches instead of tapping on MacBooks but you gotta draw a line somewhere.
HTTP/1.x is not obsolete. It fills a very relevant request structure that most of the Internet still runs on.