To be super clear, I mean "SSR" in the way it's practiced in the JS world today. Specifically "run the JS on the server, ship a snapshot, then ship the JS". I'm *not* dunking on PHP-era "output HTML, the end". That pattern is *fast*. "SSR" can be good if we omit the cilent JS
-
-
Show this thread
-
You can also ship just enough JS, in small enough chunks, to put responsive UI on screen fast. That's great too. It's the uncanny valley + long tasks that SSR creates today that is junk architecture.
Show this thread
End of conversation
New conversation -
-
-
Thank you! I feel like I’m taking crazy pills! Didn’t we have an entire multi-year SSR craze like 9 years ago and came to the same conclusion? But it’s React now so somehow it’s different?
-
9 years ago is how many bootcamp/accelerator/"full stack" classes?
- 9 more replies
New conversation -
-
-
This Tweet is unavailable.
-
Yeah, there's a big chunk of the internal world here that seems to think delayed JS delivery works out often enough from our infra that it's generally OK. I remain skeptical. Turns out I'm out of alignment with most of my co-workers too!
End of conversation
-
-
-
I think the SSR (yellow) vs CSR (blue) chart shows that..... * TTFCP is faster in CSR * Engagement is down with CSR Doesn't this show that SSR is better for engagement here, even if TTFCP is slower? How did you interpret the case study as "SSR is bunk"?
-
Yeah I failed to follow the logic of "don't SSR" based on the case study. In fact it points to the opposite, especially for low end devices. Right?
- 1 more reply
New conversation -
-
-
Their experiment to move away from SSR failed because low end phones, which isn't surprising: 1. Any server is going to be faster than any phone. 2. Browsers are insanely fast at rendering HTML.
-
Would love more data on this! Not surprising (particularly if it's the "usual suspects" stack), but hard evidence is super valuable.
- 4 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.