ivanfranciscoj

In general, I agree, I have two cases where mixing server and client is a good idea. 1— When you have a heavy NPM package, and you are using just a small portion of it, for example, charts libraries, if you render the HTML in the server, you can send only the HTML to the client instead of sending the entire package and waiting for a client to do the rendering. 2- SEO

The idea of skipping maintaining a REST API is cool, but it only works (in a normal project) for some specific use cases; most of the time, having a regular endpoint in a REST API is more accessible to implement. I am saying there are use cases for server actions and some perks, but the future is still with classic requests to endpoints, and "server actions" are more a tool than a standard.