I continue to be be amazed at how a vastly superior architectural pattern – generate HTML on the server, then optionally add to it on the client – became something other than the default choice
Alex Russell @slightlylate
31 Oct 2019
Replying to @slightlylate
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
12
48
3
111
So far I saw server side/client side/hybrid as simply having different tradeoffs. What make it vastly superior in your opinion?
2
3