3 ms·
Ops wins should just be assumed, though. Not to be flip, but you'll gain performance wins picking just about any other language/stack than Ruby on Rails. Even P
by themartorana 10y ago
Ops wins should just be assumed, though. Not to be flip, but you'll gain performance wins picking just about any other language/stack than Ruby on Rails. Even Python blows it out of the water. Move to something like Erlang/Elixir with a ridiculously nice/tuned runtime, or compiled languages like Go, or a combination of the two like Java/.NET and you should see huge performance wins without much work.
Rails wins in some cases for development productivity, and is "good enough" for many things. But when it's time for scaling, the language/solution/stack choice almost doesn't matter if you're moving from RoR. That said, if free ops performance wins aren't part of the decision, you've done it wrong.
- rdtsc 10y ago> Ops wins should just be assumed, though They should be, but often they are not I. It is mostly about "Look how fast it runs on my laptop, it means we can have millions of requests on a large server". I've heard people quote Techempower benchmarks as their reason to picking a language / library vs another.