2 ms·
It depends on what you're doing, really. If you write something in Ruby that then performs like a dog and you have to rewrite in Erlang to get to anything remot
by jerf 16y ago
It depends on what you're doing, really. If you write something in Ruby that then performs like a dog and you have to rewrite in Erlang to get to anything remotely "web scale", I hope you learned a lot about your problem domain in Ruby because otherwise that's a pretty big waste of time.
I personally tend to use Erlang in the core of the product as the internal router and basic message bus, with the ability to "drop to" Erlang if I need to, but leave a lot of the business logic in higher-level languages in processes connected to the core. I don't necessarily want business logic in my Erlang, but I wouldn't even try to prototype a router-like program in anything but Erlang, because nothing is better at it than Erlang.
- davidw 16y agoThat sounds like a sensible way of doing things. > I hope you learned a lot about your problem domain in Ruby because otherwise that's a pretty big waste of time. The biggest problem most startups have is no market, not being "web scale". You'll figure that out faster with Rails or Django as your web code. Clearly there are some areas where Erlang is really, really unbeatable, but... my whole point was that I see other people muscling into them, like node.js and Scala. Are they there yet? No. But give them some time and momentum and they'll get most of the way there; far enough for most people.