> Elixir abstracts that away and leaves a ruby-like language that hides much away - which good and fine. Processes, message passing, and behaviours are all com

> Elixir abstracts that away and leaves a ruby-like language that hides much away - which good and fine. Processes, message passing, and behaviours are all completely first class in Elixir. There's no hiding. `spawn` is `spawn`. `send` is `!`. `GenServer` is `gen_server`. `@behaviour` is `-behaviour(...)`. The entire Erlang stdlib is available directly. We use processes, messages, and behaviours all the time in regular Elixir work. Elixir adds a different syntax (note that I did not say better), a macro system, a protocol system, its own stdlib functionality, some better defaults, and a build tool. It's perfectly fine and reasonable to prefer Erlang (I learned Erlang before I learned Elixir), but for the benefit of other readers, they are really not that different. The distance between Elixir and Erlang is very small. They could almost be seen as dialects.