So... this is so funny because it feels like you totally missed my point. I did not talk of reading documentation because i am literally one of the person you

So... this is so funny because it feels like you totally missed my point. I did not talk of reading documentation because i am literally one of the person you should come to if you need something in the doc. I learned how to write elixir and erlang by reading their doc. I also do not use an IDE and am really relucant of them because i don't find them useful. And I am a big defender of prolog. And i am not denying the strong architecture and infrastructure of erlang. I literally contribute to it. But what you have not addressed is ... all I mentioned. The broken testing libraries. The inability to do the right thing nicely because the parse transform are a pita. The fact that modules names cannot be aliased, generating painful to navigate file structure and names. Etc etc. And look. It can be made better. We have worked on documentation and there is more coming. We are getting multiline strings. Rebar3 mostly work. Hex can be used for erlang projects. But in order to do things better we need to acknowledge the problems. Not just say that the kids don't understand. Especially when the person you say that to is actually understanding it pretty well thank you.