Great summary. We indeed switch to Websockets for a few things that we would like to have (eventually) used HTTP/2 Push for. To give an example of an issue wit

Great summary. We indeed switch to Websockets for a few things that we would like to have (eventually) used HTTP/2 Push for. To give an example of an issue with this, is that we would like to receive updated resource states when they happen. Receiving these via websocket unfortunately means that they can't really interact with the browser cache, which led us to implementing our own Javascript caching layer. There's many small examples of this where the ideal approach doesn't exist yet, and we're left to imperfect workarounds.