<story><title>Intent to unship: HTTP/2 Push</title><url>https://groups.google.com/a/mozilla.org/g/dev-platform/c/vU9hJg343U8/m/4cZsHz7TAQAJ</url></story><parent_chain></parent_chain><comment><author>saurik</author><text>It is extremely annoying that all of this sudden discovery that http2 push didn&amp;#x27;t work hasn&amp;#x27;t come with some kind of apology to everyone out here who had tried to explain before why this wouldn&amp;#x27;t work and why it would be a dangerous waste of time just to be shouted down for years by the people insisting it was going to be epic as the much-smarter people at Google knew what they were doing and really needed this so we should just let them ram it into the spec. We should be extremely conservative about what we put in the spec and stop just throwing in speculative stretch goals because some people at Google thought it&amp;#x27;s a good idea.</text></comment>
<story><title>Intent to unship: HTTP/2 Push</title><url>https://groups.google.com/a/mozilla.org/g/dev-platform/c/vU9hJg343U8/m/4cZsHz7TAQAJ</url></story><parent_chain></parent_chain><comment><author>pornel</author><text>You can get some of this speed back with HTTP&amp;#x2F;3 0-RTT start, and use 103 Early Hints to make browsers preload assets early. This combo has an advantage of being semantically backwards-compatible with HTTP&amp;#x2F;1 (reverse proxies, load balancers).</text></comment>