[knowmad]

Don't get me wrong RoR is great and it is definitely the fastest way to get a project out the door and in front of your users. I've just seen what happens when that project takes off and you end up with a massive monolith that you're paying through the nose to support with the biggest RDS DB available, and every change you make has a 50/50 chance of introducing a bug somewhere else in the system. Then, because of those issues, you decide to split up the monolith into microservice, but you have a bunch of RoR engineers that have been working with monoliths their entire careers so you end up with a distributed monolith that's even harder to change and requires coordinated deploys.

I recognize that there are definitely ways to scale RoR well (GitHub, Shopify), but the framework is designed to get you up and running as quickly as possible so trade-offs were made in areas that

[knowmad]

Edit: Trade offs were made in areas that make it fast to build simple apps, but don't lend themselves well to apps at scale. "Rails Magic" in a simple app becomes "Rails Witchcraft“(arcane and dangerous) in a complex app