I've been closely following Elixir since it was announced and I should've made it clear that I still think Elixir is a fantastic project
At first I though it would be my doorway into Erlang programming (or Reia, at the time), with the familiar syntax and all, but eventually I learned Erlang and wound up actually enjoying it. Then, an opportunity arose to use Elixir but, because of its early stage (this was right between 0.3 and 0.4), I couldn't deploy it in a production environment, so I ended up choosing Clojure.
So now, between Erlang and Clojure, I can't see where I could justify using Elixir. It's just my personal experience, of course.
> Unfortunately, extending the Erlang VM is nowhere close to extending the Java VM. :(
No need to; one could just adapt ClojureScript to spit out Erlang. It would depend on the JVM and wouldn't support native macros, but it would work ok, I guess.
> The problem with the OO approach is that OO didn't suit well an immutable language.
I think you made a very wise choice when you ditched OO. I'm all for functional & immutable.
> We are exchanging the OO familiarity by a better/tighter integration with Erlang runtime, which will, hopefully, be a good reason for people to try it out.
I understand it might be premature, but I would love to know what kind of projects/developers is Elixir attracting?