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
Vastly superior, really? If you want to implement an application, would you implement it by generating a bunch of PDFs each linking to another PDF?
2
1
Replying to @spion @ScottWlaschin
Yes, vastly superior, and the PDF analogy is completely broken.

Nov 1, 2019 · 10:08 AM UTC

1
4
Replying to @stilkov @ScottWlaschin
Its exactly on point, and illustrates the giant hack that is server-side rendering perfectly by offering a bit of perspective.