pre-rendering then hydrating an identical DOM is just rendering twice (twice as slow)
This assumes the JS that comes down the wire doesn't create large dead temporal zones for interactivity, either because UI doesn't work w/o it and it's large (or delayed) or because it creates late long tasks for other reasons. In all cases, smaller JS is better.
-
-
Yes. Absolutely. That'd be a constraint I'd impose. We haven't a way to impose that without arbitrary boundaries on state. That's the crux of the performance conundrum. The only constraint we accidentally agree/code split on is the complete URL.
-
It's mad how this is still a thing. I've been out of the loop on this stuff for about 7 years but not damn thing changed

- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.