3 ms·
I did Rails for 10 years. This is not even a trade-off anymore. You can write code in a productive language and have it be much less resource intensive out of t
by sjtgraham 10y ago
I did Rails for 10 years. This is not even a trade-off anymore. You can write code in a productive language and have it be much less resource intensive out of the box, e.g. Elixir.
Your codebase is as good as your worst developer and it's quite easy to write faulty code in Ruby. The claims of any savings using Ruby are highly dubious in my experience of making lots of money being called in to unf*ck many a Ruby codebase as a contractor.
- grobaru 10y agoSorry but everything is relative and we could have just stick with JVM and Java as it's super performant and you have enough developers to choose from. Picking elixir over ruby is like picking a katana when you want machete.
- qaq 10y ago"Perfomant" is very relative if I care about worst case latency BEAM outperforms JVM. Elixir is about as productive as Ruby yet about 10-15 times faster. To me BEAM/OTP's features more than make up for the slower number crunching performance compared to JVM.
- claudiug 10y agooffcourse. every rails/ruby thread must have an elixir reply. every time. Sorry to bashing, but that is the reality
- technion 10y agoI'm surprised we don't see more "use jRuby" replies. Most of these discussions come from businesses "already using Rails". jRuby has immediate, major improvements to performance and many codebases "just work". In my case, I just had to mess with the Gemfile a bit.
- hhandoko 10y agoMost Elixir and/or Phoenix migrants I met came from Ruby / Rails shop [1], and those who have made the switch seems to be very happy with their decision. [1] Probably because Elixir is Ruby-like, and Phoenix has some Rails feel to it (so I was told).