> But you are keeping dismissing the interoperability part. Since you are now sending fully rendered browser specific output you loose your chance to use the sa

> But you are keeping dismissing the interoperability part. Since you are now sending fully rendered browser specific output you loose your chance to use the same backend for different type of clients, such as mobile apps or other tools that can work with your system. It really depends on what you are building and if the interoperability is a requirement vs costs and simplicity. I was part of a 4 person engineering team, all who are full stack, that built an app in Rails, started with server side rendering and later on moved to React, but much of what we had were still serverside rendered html. But our mobile app was done in Cordova and we didnt have to pay for mobile engineers (who usually are exclusively mobile) and to build out APIs for the mobile client. As a result our team was able to move multiple times faster than another team that had 4 frontend 6 backend and 8 mobile devs. There are inherent costs when you have multiple teams/components or even specializations, especially around coordination and communication.