Re:Elixir v1.1.0 Released
by chrismccord on Friday September 25, 2015 @11:49AM
(#10278803)
The easiest sell to clients and stakeholders is reduced operational overhead, lower costs, and higher reliability. Real-world stories are coming out of 10-20x reduced server counts from Ruby and Python systems that have been replaced by Elixir. We also have stories like WhatsApp (Erlang) who supports their hundreds of million of users with a few dozen engineers. The dollar cents here make it a strong sell to stake holders, and the platform features make it a strong sell to the rest of your team and software requirements.
[ Parent
| on HN ]
We have also heard stories such as LinkedIn, Netflix and Twitter migrating from different languages (such as Ruby for Twitter) to Scala. How do you think this success story of building distributed concurrent backends compare to Elixir's?
Objectively: Scala is dramatically larger than Elixir as a language. Akka is much larger than OTP.
Personal, subjective conclusion: Scala is substantially more complicated to use and learn than Elixir (to achieve the same ends).
Personal, subjective remark: Scala is substantially more complicated than Haskell. It's just so big.