[nickjj]

> The obvious performance and bloat overhead with RoR aside.

Does the bloat matter in the end tho?

You can build a million dollar business on a single $20 / month DigitalOcean server to run everything with tens of thousands of users. That's what Chris did from https://gorails.com. We talked about his Rails driven tech stack on the Running in Production podcast[0].

Recently he tweeted out he generated a million dollars from his business[1].

If you can get 100ms or less p95 response times without a complicated infrastructure then the only thing that matters is the ecosystem, community and how much you enjoy using that technology. If performance is a web framework's biggest feature then I think they're fighting an uphill battle. Performance isn't that important for most applications as long as you can produce a nice feeling application that responds quickly. All modern frameworks have a means to do that. Now it comes down to how fast can you build it and how nice is it to maintain.

[0]: https://runninginproduction.com/podcast/12-learn-ruby-on-rai...

[1]: https://twitter.com/excid3/status/1295730795148193792

[fareesh]

I guess it depends on what you build. At the scale of GitHub and Twitter or Shopify there are probably significant challenges caused by said bloat.

[untog]

But once you reach that level of scale you have (or should have!) the resources to redevelop services that are holding you back. Not choosing Rails because you intend some day to get to Twitter scale smells of premature optimisation. (Twitter themselves used Ruby!)

[fareesh]

Yep, which is generally why I can't see a good argument for not using it. I was hoping to see some here but it seems to be a consensus view.

[cardy31]

I would argue that there isn’t a framework in existence that is actually built to cleanly scale to the size of any of those companies. If there is one that claims to, it is probably lying.

[abhiyerra]

I have had to help scale a large scale Rails app and break it apart about 5 years ago. 500k requests per minute. That was tough. A lot of the features that Shopify and Github have upstreamed since then would have helped a lot and to be honest it is a lot easier to scale now with Rails because of those upstreamed features. Like multiple databases, viewcomponents, etc.