> Real-time chat is the most obvious case where the html purist won’t offer an acceptable experience. The retro approach is to have two frames. One to submit,

> Real-time chat is the most obvious case where the html purist won’t offer an acceptable experience. The retro approach is to have two frames. One to submit, one to slow-stream a bunch of html elements which we can thankfully now lay out via flexboxes which are highly efficient when it comes to relayout, i.e. only the appended elements would incur some runtime costs, the already rendered ones don't get recomputed. I have seen chan-style imageboards that update posts as people type (every dozen milliseconds) with 10k posts in a thread. The layout recomputation overhead is really low.