4 ms·
Sounds like reasons to prefer FP over OOP, not necessarily Erlang. I do really appreciate Erlang / Elixir (have contributed several libraries), but the problem
by stingraycharles 8y ago
Sounds like reasons to prefer FP over OOP, not necessarily Erlang.
I do really appreciate Erlang / Elixir (have contributed several libraries), but the problems you describe are not uniquely solved by Erlang. Akka / Scala is another take on the whole actor based architecture, and seems to have considerably more traction (hiring talent will be easier for your manager).
- wrong_variable 8y ago> but the problems you describe are not uniquely solved by Erlang I agree, I do not any Scala / Akka experience so I cannot argue for or against due to ignorance. But as you say at least the platform / language addresses these concerns.
- innocentoldguy 8y agoWhere I live, it is easier to find local Elixir talent than Scala. There was a big Ruby community here and many of them have moved to Elixir.
- pdimitar 8y ago> Akka / Scala is another take on the whole actor based architecture, and seems to have considerably more traction (hiring talent will be easier for your manager). They solve a subset of the problems that Erlang's OTP solves. They don't have the entire package.
- yawaramin 8y agoYou should really read jhgg's response describing the BEAM runtime's pre-emptive scheduling of its lightweight processes: https://news.ycombinator.com/item?id=19241194 https://news.ycombinator.com/item?id=19241194 . No other runtime can do that for you, not even the JVM.