Re:Thoughts about the cutting-edge of server programming
by vezzy-fnord on Thursday August 13, 2015 @09:51AM
(#10054121)
Please do not give undue preference to Elixir over Erlang.
Other than that, I agree.
Re:Thoughts about the cutting-edge of server programming
by anonyfox on Thursday August 13, 2015 @09:57AM
(#10054178)
I used both, Elixir/Erlang and Erlang/Elixir. And Both variants exactly one time. The only small preference is that I used the Elixir/Erlang variant as the first one, but hey, one could argue that coming from Go/Node, elixir may be easier to get started. :)
Re:Thoughts about the cutting-edge of server programming
by vezzy-fnord on Thursday August 13, 2015 @09:59AM
(#10054193)
What are "Elixir/Erlang" and "Erlang/Elixir" supposed to mean? I understand adding the slash for OTP, as those are shared traits. Perhaps their use of BEAM, though that's secondary.
not really.
By the way, have a look at http://blog.plataformatec.com.br/2015/06/elixir-in-times-of-... . Elixir/Erlang excels at concurrency and allows you to build large-scale distributed backends easily, with many additional benefits (fault tolerance, ...).By the way, "Microservices" and "Actors" for parallelism and concurrency aren't really discussed in the erlang/elixir world, since this is the natural way to code. The "cutting edge" to do massive backends is actually decades old, battle-proven and guaranteed to work, this is what erlang actually was designed for.
Many many Big systems today are using the Erlang VM for their critical backends, like Call of Duty or Whatsapp.