We need to talk about Redux and "SSR". Just saw second (large, commercial) site sending > 100/500K (zipped/unzipped) of HTML payload *this week*. When it takes 3-5x the size of a PNG screenshot of your AFT content to "inline" your "critical" HTML/JS/CSS, something's broken.
-
Show this thread
-
Replying to @slightlylate
Wild. I'd like to point out that many apps wouldn't do SSR at all if it was significantly more complicated than what Redux offered. And that if you don't care about performance and do basic profiling, you can run any tool into the ground. But it's fair criticism of the model.
2 replies 0 retweets 6 likes -
Replying to @dan_abramov @slightlylate
I think that many (bad) developers look at SSR as basically a Silver Bullet, they're not thinking critically - "what should I inline", they're just applying it to everything to "make it faster". Encouraging folx to only SSR *some* things in the tooling I think would help
1 reply 0 retweets 2 likes -
I mean that's kind of the general problem I see
@slightlylate point out. That devs expect to be able to build good complex experiences without learning fundamentals like "how to minify JavaScript" or "what should my initial payload weigh".2 replies 1 retweet 2 likes
In nearly all of these cases, the user experience would be better if the SSR'd content dropped all <script> tags. This architecture works on the server-side where CPU is cheap. Extending it to the client isn't working.
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.