<i>Are you saying HTTP&#x2F;2 &#x27;re-implementing multiple connections on top of a single TCP stream&#x27; is a bad thing?</i><p>Not necessarily; I&#x27;m saying that it is another layer of multiplexing on to of a layer of single connections, that is on top of multiplexing, which is on top of a single connection, etc.  I&#x27;m saying that the main reason HTTP&#x2F;2 exists is because of the limits we had to put in place in HTTP&#x2F;1.1, like connection limits, and the uphill battle it is to get standards changed like how TCP window size works or how to deal with slow start.<p>Eventually, we&#x27;ll come full circle le when someone uncovers an optimization that occurs when you make multiple TCP connections to a server, all running HTTP&#x2F;2 over them.