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.
-
Show this thread
-
Replying to @slightlylate
Tell me more - I need to prepare for a second wave ;)
1 reply 0 retweets 0 likes -
Replying to @sergeyche
Oh god, it's endless BS. At least half the time I get a team to admit they don't need SSR (assuming they don't break the experience with JS), they still claim it's a requirement for reasons they can't articulate.
3 replies 0 retweets 1 like -
Replying to @slightlylate
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.
1 reply 0 retweets 0 likes -
Replying to @sergeyche
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.
5 replies 0 retweets 1 like -
Replying to @slightlylate
I am with you. but, I am afraid they will kick me out of the company if I suggest not to use JS on the front-end. That being said, there is no need for TTFB hit either - with static generation workflows. And they are possible in more cases than current SSG industry believes.
1 reply 0 retweets 0 likes -
Replying to @sergeyche
RedactJS is a tourniquet; the answer (from there) is to progressively enhance the SSR'd output (WC anyone?), but trust many fewer people in the org to push code to the client.
1 reply 0 retweets 0 likes
Fundamentally, this is a management failure: managers didn't understand their customers deeply and didn't investigate the downsides of the tech they greenlit. RedactJS lets managers who have learned better start "fresh" w/o throwing it all out.
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.