Sounds like you didn't really invest much time in the former, or that post-hoc experience made it easier for you to understand, but you instead flocked over to Elixir.
There is no easy path to Erlang. When you learn a new programming language, what you are doing is creating an implementation of that programming language in your brain (including a tokenizer, parser, and interpreter).
The reason people go EWWW at Erlang is they don't want to struggle to implement a new tokenizer and parser in their brains. They just want to learn one tokenizer and syntax forever then pretend that's all they ever need, all while basking in the superiority of their ignorance.
I certainly consider that Elixir will lead me to love Erlang, but with a reduced initial friction (like CoffeeScript did for me with JavaScript, which I'm now confortable with).
I looked at Erlang a while back but passed (didn't "click" for me), yet I'm now learning Elixir (which totally "clicks") to complement Ruby in polyglot apps.
I can safely state that I'll very soon use Elixir in production (ETL first, then web/API).
A very useful skill to have if you do consulting on the long run (like I do) is being able to evaluate what to invest in and what to pass on. My own evaluation is that Elixir is going to work very, very well on the long run.
Just another opinion :-)