|
|
|
|
|
|
by TeMPOraL
3300 days ago
|
|
|
In theory, maybe there is an argument. In practice, most of the time it'll be a pretty bad one. For me it's about how user-hostile those decisions are. I can understand SPA-s when e.g. the service would be infeasible if all the processing was done server-side. But more often than not, it's just laziness. The devs can deploy a sleek-looking SPA in 5 minutes with their JS toolchain, forever dooming users to download tons of pointless JS that adds nothing valuable to their experience. But who cares, today's zeitgeist is "privatize the profits, socialize the costs". Think of all those sites with articles and blog posts that blank out if you have JS disabled. There's no reasonable argument to be made that they should be SPA. That's just a case of user-hostile laziness. |
|
|
Oh, if that'd be true...
Our experiments with React took quite a lot of time (like, weeks) before we got things in shape. And then some more time before that shape wasn't a pear.
And if the backend is not in JS, server-side rendering is quite a mess.