[rwalle]

I am surprised that this topic keeps coming back and gets attention. I thought in the year 2023 this is a settled topic.

Lots of hype from people who obviously never managed a real website or a real-world software project.

On the non-technical side, traditional server/client separation is well understood by everyone and has all the tools any team ever needs, while SSR takes some learning -- it is added cost that does not transfer in many places.

On the technical side, SSR only has clear advantage for very specific scenarios, e.g. e-commerce site where rendering time and responsiveness across different devices is a top priority. For the vast majority of websites out there, SSR likely only increases your server load and cost when you could leave all the rendering to client which is free resource. As browsers and computers themselves get faster, you don't even need to do anything to get better performance on client machines. Otherwise, this does not matter any more than Pepsi vs Coca-Cola or vim vs emacs.

If SSR is clearly the better choice for a team/product, go ahead, otherwise don't waste time on it.

[halfmatthalfcat]

Server Side Rendering been established practice for a long time, going back to PHP/JSP/etc. It's just taking on new life the past couple years. There's pros and cons to both server and client rendering.