2 ms·

Longtime Rubyist here that has worked with Elixir. It is only loosely based on Ruby's syntax - there is a _lot_ more punctuation in Elixir. Also much more expli

Longtime Rubyist here that has worked with Elixir. It is only loosely based on Ruby's syntax - there is a _lot_ more punctuation in Elixir. Also much more explicit passing of parameters, including database connections and error handlers in the case of a Phoenix application. It's also a challenge to deploy OTP along other non-hypervised runtimes. BEAM and Elixir are very cool, don't get me wrong, but after some programming web services in Elixir I was ready to head back to Ruby. If I need a highly fault tolerant near realtime comms system, I'll look at Elixir, otherwise I avoid.

whalesalad 3y ago
> It's also a challenge to deploy OTP along other non-hypervised runtimes. Pardon?
- ungamedplayer 3y ago
  This part stumped me too. Maybe op had some deployment issues on VM systems.
  - whalesalad 3y ago
    ngl I get a sense the op and most people commenting in this thread don’t understand elixir at all. the fact that the syntax somewhat resembles ruby is really just 5% of what makes elixir interesting. It’s a distraction from the real value of the beam, OTP, and immutable data.
rozap 3y ago
> It's also a challenge to deploy OTP along other non-hypervised runtimes. What in tarnation. Please expand on this one.