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
I see it as a confirmation of conways law. I always experienced a strong division of front- and backend, to the point where companies ordered the FE from one agency and the BE from another...
1
6
Replying to @mkhl @ookami86
Agreed, though I don’t think it’s the only one

Nov 1, 2019 · 8:37 AM UTC