Earlier quoted context omitted.
> Hansson created Rails It sounds like the old adage, "the architecture of the company mimics the architecture of the software," applies very well here. In this case, the company's stance on politics scales about as well as Rails.
Shopify and Airbnb were able to become multi-billion dollar companies mostly by running on Rails before it became unsustainable. I'd say Rails scaled pretty well.
Now, Shopify clearly has the capacity to pull this off. But a smaller company that initially bet on Rails and is now facing a mountain of tech debt might not. To be fair: it is possible to write Rails applications in a way that you don't couple every aspect of your application to Rails internals. But in certain crucial ways, Rails encourages doing exactly that - dragging the DB along your whole application, for example.
I've been a Rails developer for a couple of years and I left that ecosystem in no small part because a huge chunk of that community seems to treat "architecture" as a dirty word and monkeypatching as a solution for everything (and also indulges into making fun of PHP or Java a bit too much for my taste). Of course, everyone's experiences are different and you can do great stuff with Rails, but for me it's something I don't really want to go back to.