[foofie]

> HTTP/1 remains the one with the highest bandwidth.

To be fair, HTTP/2 and HTTP/3 weren't exactly aimed at maximizing bandwidth. They were focused on mitigating the performance constraints of having to spawn dozens of connections to perform the dozens of requests required to open a single webpage.

[Beldin]

Too bad that the alternative option - not requiring dozens of requests just for initial rendering of a single page - didn't catch on.

[GuestHNUser]

Couldn't agree more. So many performance problems could be mitigated if people wrote their client/server code to make as few requests as possible.

Consider the case of requesting a webpage with hundreds of small images, one should embed all of the images into the single webpage! Requiring each image to be fetched in a different http request is ridiculous. It pains me to look at the network tab of modern websites.

[foofie]

I don't think it's realistic to expect a page load to not make a bunch of requests, considering that you will always have to support use cases involving downloading many small images. Either you handle that by expecting your servers to open a dedicated connection for each download request, or you take steps for that not to be an issue. Even if you presume horizontal scaling could mitigate that problem from the server side, you cannot sidestep the fact that you could simply reuse a single connection to get all your resources, or not require a connection at all.

[eptcyka]

HTTP3 also wants to minimize latency in bad network environments, not just mitigating the issue of too many requests.