[headcanon]

Perhaps, but what about this:

1. Easy to deploy

2. Integration tests are a breeze

3. Debugging is a breeze

We use a distributed architecture in clojure and python where I work, but it has its own downsides, and for a lot of people monoliths are a much better solution.

[patsplat]

There's a separate argument to be had about single process vs multi process backends, but that gets away from the core premise of Rails. Part of that premise included opinions and defaults about client-side development.

Rails was unique in its time in that it shipped with solid client-side DOM manipulation (prototype.js). It supplied a "full-stack" framework that made it easy to build a dynamic, AJAX Ux.

But lately the "best practices" in the node ecosystem move so fast that any default may soon be outdated. What would today's javascript Ux best practice be? Vue.js? React? Angular? Which state management solution is "best" ? Which CSS framework is "best" ?

Any choice you make will be out of date by the time you ship. There's a ton of activity. It's a decision that belongs on the project, not the framework.