Also, can we just stop and note how weird it is that we're talking about a low-latency network and desktop CPU in 2018? That choice surely needs exposition. One of the reasons I'd have thought SSR would be a win is that it largely removes client CPU from the equation.
It's a good thing browsers implement threaded scrolling, else *nothing* would work in those 5 seconds of red.
-
-
I don't mean to harp on this to make Fastboot look bad. It's got exactly the same problems as most of the React SSR solutions I've seen deployed. This isn't unique.
-
Yeah, what's running on the FastBoot site is quite old and materially worse than the React SSR implementation. In the LinkedIn feed experiment, we moved to an incremental rehydration model that uses requestIdleCallback to prevent post-JS thread lockup.
- 8 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.