> Push required knowing what to push, Could have been as simple as once-per-resource webpack build step which detected all resources downloaded per-page (easy

> Push required knowing what to push, Could have been as simple as once-per-resource webpack build step which detected all resources downloaded per-page (easy with a headless chromium), and then pushing all of those (or all of the non-cacheable ones if the client sends a recent cookie). Yet frameworks and build systems didn't do that, and the feature was never really used. > you can actually slow down the page load (like pushing resources the client already started downloading). Any semi-smart server can prevent that, because it already knows what is currently being transferred to the client, or was already transferred in this session. There is no race condition as long as the server refuses to double-send resources. Granted, some server side architectures make this hard without the load balancer being aware. This compression dictionary will see the exact same fate IMO.