It is, but I'm of the opinion that HTTP needs more than pragmatism to solve its woes at the moment.

The latency issue with the protocol is just immense and this takes a whack at a main issue, but doesn't quite get to where it should. One of the main drawbacks is you still have to wait for the first reply before you can request any associated content, which is bigger deal than it seems. The second drawback is it requires the website owner to do this by hand and invariably they'll bundle things in the wrong way, not account for differing network bandwidth types or simply not do it.

That said, for some very good reasons, this is good direction, so we'll see what happens.

The author has knowingly traded off technical style points for practical ones, a tradeoff I applaud. So often the opposite choice is made, resulting in beautiful little laboratory experiments that have little relevance in the real world.