You are on the right track however you missed one huge topic that drives a lot of decisions surrounding the client server relationship: cybersecurity. One of the other reasons to use Web Assembly other than developer ergonomics is that it runs in a sandbox.
You touched on throttling which is important.
When developers make a product more client heavy it’s most likely not by choice, but necessity or lack of backend expertise.
One problem that SPA causes is that webpages are no longer statically analyzable by web crawlers, in other words they are not search engine optimized. Server-side rendering of SPA solves this issue and shifts some of the heavy lifting rendering DOM back to the server but now it’s more dynamic rather than static.
You are on the right track however you missed one huge topic that drives a lot of decisions surrounding the client server relationship: cybersecurity. One of the other reasons to use Web Assembly other than developer ergonomics is that it runs in a sandbox.
You touched on throttling which is important.
When developers make a product more client heavy it’s most likely not by choice, but necessity or lack of backend expertise.
One problem that SPA causes is that webpages are no longer statically analyzable by web crawlers, in other words they are not search engine optimized. Server-side rendering of SPA solves this issue and shifts some of the heavy lifting rendering DOM back to the server but now it’s more dynamic rather than static.
Or maybe they're just enjoying the ride on the SPA hype train and can't think outside of that box.
Why I ignore the hype (and you should too)
Steve Belovarich ・ 3 min read