The exhausting thing about "SSR" conversations is that they always seem bottom out at Brandolini's Law, one exhaustive debunking-via-trace at a time.
-
-
OK, looks like we have different opinion on the topic - I feel that SSR with tiny TTFB (static) is necessary simply because "they don't break experience with JS" is a very hefty assumption. Filmstrips I'm looking at are horrendous. That being said, CPU impact is there as well.
-
I'm a huge fan of "RedactJS" approach where you take SSR TTFB hit and then *don't send the script* Modern frontend doubles as a functional PHP. It's the client-side were it's toxic.
- 3 more replies
New conversation -
-
-
BTW, I wish people thought of all this for User Experience reasons, but it seems that Developer Experience and Bot Experience (SEO) are more important.
-
I *guarantee* the people waving those flags don't know what they're talking about. If they did, they would have quietly pulled them down, respectfully folded them, and never mentioned them ever again.
End of conversation
New conversation -
-
-
What is usually worse, impact on TTFB or extra delay caused by rehydration?
-
This is part of the problem: the set of caveats and wherefores to begin to answer *even this direct question* tends to swamp the level of understanding that teams who are buying into "SSR" tend to exhibit.
End of conversation
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.