I might be wrong, but is there real evidence that HTTP/2 "solves" the HTTP head of line blocking issue, in a disease was worse than the cure sort of way? Of cou

I might be wrong, but is there real evidence that HTTP/2 "solves" the HTTP head of line blocking issue, in a disease was worse than the cure sort of way? Of course the reason people try to multiplex higher level protocol streams over TCP is some butt-hurt over cost/availability of multiple TCP connections and a desire to make the higher level protocol appear to have more "parallelism" than is really there. In the case of HTTP so that e.g. you are not forced to use sprite-sheets, data-urls, or just less bloat in order to minimize load latency. My experience so far is that in practice this rarely works out, you end up with nastier TCP level issues instead and I get the impression that this has been the actual experience with HTTP/2 as well. In that case the stupid part would be assuming that multiplexing over TCP is a good idea, despite various cautionary tales to the contrary. As I said, I haven't looked into this carefully so my superficial impressions might well be wrong, which is why I'd appreciate input from someone who has properly looked into it.