Last evening I saw a demo of a SSR @angular app that had partial client-side component hydration triggered only by a mutating user action.
This meant that not only was there 0 JS overhead to render the app, but that users only paid the runtime cost for what they interacted with
-
-
What was the point of this tweet?
-
What was the point of yours?
- 1 more reply
New conversation -
-
-
Bla bla bla bla
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Please tell me the tomato sauce hydrated in time. Cause I hate losing reception in a tunnel and ending up with nothing between the cheese and the crust but a dry 404.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Hahahaha
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
This Tweet is unavailable.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.
he/him 
