Are you saying HTTP&#x2F;2 &#x27;re-implementing multiple connections on top of a single TCP stream&#x27; is a bad thing?<p>There is an entirely valid reason to do so (that TCP connections need to have slow-start to avoid congestion). TCP will always be inefficient for sending single, small files.<p>HTTP&#x2F;2 doing this is great, because it means you can do away with the hacks that were used with HTTP&#x2F;1.1 to get around connection limits, and you can do away with the hacks like putting all your JS in a single file to get around slow-start (by reducing the number of files sent), which is bad for caching (if users have your site cached and you change one JS file, their browsers have to download the whole concatenated collection of files again).<p>I&#x27;m all for trying to keep things simple, but I think much of the complexity in HTTP&#x2F;2 is solving valid, real problems that will improve the speed of the web, which is a good thing.