For a long time browsers, both Firefox and Chrome had a bug that if you HTTP2-pushed resources, it re-fetched them anyway. But since that got fixed in both brow

For a long time browsers, both Firefox and Chrome had a bug that if you HTTP2-pushed resources, it re-fetched them anyway. But since that got fixed in both browsers I've used HTTP2 push extensively when optimizing web applications. For example instead of first requesting the main html-file, parsing it, requesting the css file and parsing it, requesting a background image, etc, both the css and the background image is pushed when the index.htm is requested. This can shave off seconds and drastically improve user experience. I've also implemented commonJS module system where all dependencies are HTTP2 pushed on the first module request. The main advantage with HTTP2 push is that is simplifies development as you do not get penalized for not using resource bundling (which complicates caching).