It's a bit sad to see the Erlang community start wearing the embracing its flaws as a badge of pride. It's a short-term solution, but long term it leads to community death. I guess I'm getting out of that world none too soon. There are reasons why it has not become more popular than it has, and if the community is going to chose to embrace them rather than deal with them, well, more power to them. You can do it without me. Which I do not mention as if that's some sort of major threat or anything, because of course it's not.
Or if they choose to run around claiming that 6 years of experience just isn't enough to get Erlang, well, more power to you too.
This is something you start seeing here and there when you try and observe advocacy as a neutral observer. I saw the same thing with Tcl a lot:
http://journal.dedasys.com/2010/03/30/where-tcl-and-tk-went-...
You have to be willing to confront the ugly truth sometimes. Of course, sometimes that means "yeah, that sucks, but changing it is more pain than it's worth", which does not fix the problem, but is at least honest.
I agree with jerf about the "ant turd tokens": they're hard to see, and irritating when you rearrange code. But the rest of Erlang has lots of good stuff, so I just deal with it.
Unifying , . ; is the most baffling one to me that I hear all the time.
But I'm glad Elixir exists and it is getting more people using BEAM.