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

Oct 31, 2019 · 10:33 PM UTC

12
48
3
111
Load newest
Replying to @stilkov
It's still the default for many of us 👍
1
3
Replying to @stilkov @ScottWlaschin
WebForms intensifies
Replying to @stilkov
SSR is good for news websites, documentation, blog, landing pages, wikis SPA-s have it's advantages, - gmail, twitter, facebook and other platforms are popular and usable because they are SPAs. admin portals, dashboards are better when they are SPAs
2