And yea, you're not going very far without digging into OTP, and Martin Logan's book is pretty excellent. Great entry on this list.
And yea, you're not going very far without digging into OTP, and Martin Logan's book is pretty excellent. Great entry on this list.
If something needed to be wrapped to make it play more nicely with elixir, for example to change argument order to better suit elixir's |> operator, or if there were other real benefits to wrapping an erlang library, then they might wrap it. Otherwise if the erlang library is good just use the erlang library.
But my main point was that when I started, I could just look to one source for language docs.
But as I dug in, I realized that to do a lot of things, I needed to look at Erlang too. And then I realized I had to understand it.
It's not bad, it's just a thing that makes learning the awesome language a lot more difficult.
For me its all about OTP, thats the difference maker with Elixir/Erlang, without that its just another functional language, with it is an incredibly powerful tool/framework for building impressive distributed fault tolerant systems.
That being said, I think there needs to be a communal effort to improve Erlang documentation. It is very terse. One of the points brought up in Garret Smiths talk: https://www.youtube.com/watch?v=3MvKLOecT1I