Server push never made any sense anyway for most subresources. The server doesn't know about the state of the browser's cache, so using server push for a subres

Server push never made any sense anyway for most subresources. The server doesn't know about the state of the browser's cache, so using server push for a subresource could cause it to needlessly push a subresource that was already cached by the browser. Maybe it is useful outside of the browser context, e.g. in gRPC.