165 karma · joined January 17, 2020
Client side rendering has become popular because it reduces server load... but unfortunately increases processing time in the browser, which can slow things down for users.
There's solutions (like Gatsby, which is its own layer of complexity) and cheats and workarounds, but the standard should be that if a page will contain the same information for a certain state on an initial load for that page, that content should be generated server-side. Anything that can't be or is dependant on browser spec or user interaction should be client-side.
I just don't believe in making the user process a bunch of repetitive static stuff that can be cached on the browser from the server or compressed before sending. There's gotta be more consideration of user experience over server minimization.
So we have a continual cycle of crime-punishment that doesn't mitigate enough, simply because the underlying problems remain, until our country stops with the "you're on your own" mentality and starts supporting social programs better.
Yah, but WE'RE DISNEY