Haha! That's very true.

The reason I'm promoting elixir instead is because I feel that it's easier to pick up in terms of how different it is from imperative and OO languages.

While you are right in how Erlang has a much longer reputation, it's odd though how it hasn't gained much popularity like other languages that have been around for that long.

Elixir seems only syntactically different, to me (with a few nifty feature additions). Erlang is a syntax for BEAM more than anything.

What makes Elixir easier to learn for OO programmers?

Three things that make the experience of developing in Elixir completely different from Erlang: Tooling, libraries, and actual language features (that aren't just skip deep).

Spend 5 minutes developing an app in Elixir and you'll realize why it's not just "only syntactically different" from Erlang.

I gave credit insofar as language features, hygienic macros and pipe ops are both wins in my book.

Which libraries and tools do you think set Elixir apart? Do you prefer it to erlang (I've seen you in #elixir-lang ;)?

Here's an old (18 months ago) exhibition of Elixir's improvements upon Erlang oddities and difficulties:

http://devintorr.es/blog/2013/01/22/the-excitement-of-elixir...

Yes, but Elixir gives you some awesome things (on top of everything available in Erlang obviously) - macros, Ecto (LINQ for Postgres) and pipe operator are my top 3.

NB: I don't use it at work or anything, just read up on it during free time.

I love a good troll :)

I'd say: evaluate both and pick what suits you.

But be aware that all of Erlang's libraries and support ecosystem are available to you when you use Elixir.

But all of Elixir's support and ecosystem are available to you from Erlang, only if you install elixir.

Indeed.

Yeah trying both is definitely the best way to go about it.