...so these traces under-sell the impact of JS size and latency on the experience. Both would factors improve with SSR. Was a cable connection chosen because most LI customers have *faster* networks than that?
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.
-
In Ember apps today, we still do too much work at runtime, particularly as part of the userland AMD module packaging. Also still too big at ~120kb for emerging markets use cases. But many improvements for both of these issues are in-flight.
- 7 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.