3 ms·
> Ruby on Rails is so slow that it needs larger computing power. That's true, but... If you measure both developer productivity and server costs and on unifie
by bigiain 2y ago
> Ruby on Rails is so slow that it needs larger computing power.
That's true, but...
If you measure both developer productivity and server costs and on unified metric, for at least some projects it's 100% worth paying for powerful servers so that you can use the unbelievable magic that a good Ruby on Rails team (or single dev) can sometimes achieve.
I've seen many times over the last 10-15 years where a good Ruby dev or team pushes out a working project in a weekend or just a week or two - for something a typical Java dev team would still be writing requirements docs and editing boilerplate from their dev tooling.
I probably wouldn't want to have to support the RoR project up to Facebook or TikTok scale. But neither Facebook nor TikTok are supporting the code/platform/decisions they launched with either. Hopefully whatever your project is, it'll start turning over enough profit to pay for a 50 person dev team to do a ground up rewrite choosing a stack based on observed user behaviour at scale rather than guesses or hopes about what users are going to need.
- andrewstuart 2y ago>> the unbelievable magic that a good Ruby on Rails team (or single dev) can sometimes achieve I don't believe that Ruby On Rails has magical developer productivity beyond other technologies. If yes, explain the mechanics of it to me. Ruby on Rails does nothing special beyond Python or TypeScript or Golang or whatever. The idea that Ruby On Rails is magically more productive is just fiction created by Ruby enthusiasts.