[cuddlecake]

Would it really matter though, whether the underlying VM is JVM or BEAM, if people don't want to code in Erlang or Elixir?

I don't think introducing the BEAM is the hard part, I think it's all about the language barrier.

[verttii]

Personally I spent most of my learning curve on the BEAM facilities rather than Elixir itself. Elixir as a language is simple and fairly imperative, it's quick to pick up.

Using the language for data transformations and such is a breeze but learning the concurrency primitives, message passing, OTP tooling and behaviors is where the real work is in my opinion, when building distributed systems on top of BEAM.

[lostjohnny]

In my experience the opposite is true.

I've been able to introduce the BEAM in a large company (where I work) but the barrier has been they don't know it, they know very well the JVM and they don't care about the language if it can produce a runnable jar.

I would really use the JVM more if I could program it in Elixir.