The only real way to learn Erlang is to spend 3 months reading the documentation from start to finish multiple times (not each API doc, just the guides), failin

The only real way to learn Erlang is to spend 3 months reading the documentation from start to finish multiple times (not each API doc, just the guides), failing to figure out why your program won't compile, fixing that missing comma or extra semicolon, screaming, then finally, one day, it will all click. Along the way, you'll also learn by experience why to never implement your own "process" but always use gen_servers (hint: multiple code reloads blow processes away). 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.