I'm not the person you replied to, but I feel the same way as they do. A fair proportion of libraries I've been using are Erlang libraries. That's not a problem

I'm not the person you replied to, but I feel the same way as they do. A fair proportion of libraries I've been using are Erlang libraries. That's not a problem -- one of the best things about Elixir is that you have that mature ecosystem to lean on. But inevitably with libraries, if you push them hard you get to a stage where you need to read the code to understand what they're doing, fix a bug, maybe add a feature or two. (Or at a minimum, understand their docs & examples, which'll be in erlang) Eg I use sockjs-erlang from elixir, and found myself forking it (https://github.com/SimonWoolf/sockjs-erlang/commits/master https://github.com/SimonWoolf/sockjs-erlang/commits/master) to fix a couple bugs and keep it up to date, since it's now more or less unmaintained by sockjs.