I've been a Rails dev for many, many years, so I'm not shitting on it. My one concern with Rails is human scaling, not so much "web scaling". A lot of big comp

I've been a Rails dev for many, many years, so I'm not shitting on it. My one concern with Rails is human scaling, not so much "web scaling". A lot of big companies use Rails and are successful at a large human scale. But one thing that is often not talked about is that they have the financial resources to hire the very best programmers in the world, and often they hire the very people who build the framework (e.g. Shopify, GitHub I think had a few members go through it, etc). This is critical when the biggest questions with Rails is: how to achieve clean code, modularity and separation of concerns; how to achieve high throughput. It doesn't surprise me that Basecamp says they never have issues with a huge monolith in Rails: they invented the framework and know their way around it. It doesn't surprise me that Shopify doesn't have issues with scalability: they have Rails core team members and Ruby engineers dedicated to creating an entire new Ruby VM. If the problems with Rails are solved by "throw the best people in the world at it" then it's a self-limited proposition. I have worked on countless Rails apps over the years, not one would pass the "this is just great code" test. They were not built by incompetent programmers. It's just that the "Rails way" needs a very heavy guiding hand behind it. In the real world that is often easy to lose: senior team members leave, you don't have time to rewrite parts of the code, you may not even have the expertise in-house to improve the codebase significantly. Bigger companies don't usually have these problems. And if you look at big Open Source Rails projects (Discourse, Spree, Gitlab), you'll often see the same patterns: 1000+ line models, non-standard Rails-way ideas like services and operators, hundreds of files all in the same place without any clear modularity... and these are not bad programmers at all. Maybe Rails at human scale is just hard, or maybe there’s something about the framework that leads to this.