> Spriting, data-inlining, domain sharding, and concatenation. These hacks are indications of underlying problems in the protocol itself. While this is true, I

> Spriting, data-inlining, domain sharding, and concatenation. These hacks are indications of underlying problems in the protocol itself. While this is true, I don't think HTTP/2 will or should negate some of these. Precomputing things like minification and concatenation will certainly reduce load and always increase capacity. Human-readable code is only useful for humans, and during transfer, storage, parsing, etc., it's just plain inefficient. Also, with spriting and concat, fewer files means more of the information you know you need is at the same place in disk or memory, speeding access at a low level.