In HTTP/2, all those requests are multiplexed across only one TCP connection per origin (each request becomes an HTTP/2 stream); so now when a packet is lost, all requests in progress are affected, rather than as few as ⅙ of them.
If you only ever make one request at a time, this difference does not affect you, because only one connection would be used under HTTP/1.1 as well.
But this case can make HTTP/2 significantly worse than HTTP/1.1 on low-quality mobile networks.
So... it's complicated. I'm not saying that HoL is a non-issue and that TCP is perfect. It's just that you're not eating the latency penalty N times and for anything that is dominated by throughput rather than latency it's even less relevant.
This problem is known as head of line blocking.
>"In HTTP/2, the single connection carries hundreds of streams. In this case, when we lose one packet, "one hundred streams are waiting for that one single packet"
Could someone elaborate on how this is worse if all of those streams are part of the some client request? Am I missing something really obvious.