Today, we have a good mix of teams that are fully on Elixir, teams that are ramping up, and teams who are still waiting for the first project that will allow them to say, “We’ll do this one in Elixir.”
Pro-tip: If you can't write a GenServer in Elixir from scratch, along with understanding all of the differences between casts and calls, you probably don't understand the actor model (at least how it's used in Elixir) very well.
Elixir brings style to Erlang/OTP.
Comparing to Ruby is apples to oranges because Ruby's concurrency and operational foundation is weak. The better comparison is Erlang/OTP vs JVM, where JVM gets the edge on optimized performance, and Erlang/OTP gets the edge on concurrency & tooling. The appeal for Scala folk would be if you don't care about the JVM compatibility or raw performance, and want an opinionated ecosystem built from the ground up around the actor model.
However, if we look at new services being developed, we use a lot of Elixir, it is our default choice.
This dichotomy is very usual in our industry. What we have reflects our entire history, and the history of tools available when we wrote all that code.
But what we write today reflects our priorities today, and the tooling available today.
Now ask me about front-end development. Yes, we have some CoffeeScript/Backbone still in production, but we aren’t doing any new work in it!