I think you got this article entirely wrong. Jlouis (the author) is an advanced Erlang user who does know the language very well. He wrote etorrent, an Erlang

I think you got this article entirely wrong. Jlouis (the author) is an advanced Erlang user who does know the language very well. He wrote etorrent, an Erlang bitorrent client in Erlang (which was also compared with combinatorrent, his Haskell version). The article isn't about bashing Erlang, but changing the perspective under which it is observed. Namely, the language isn't about parallelism, but parallelism is a nice-to-have feature made possible by the concurrency constructs of the language, which themselves come from a need for fault-tolerance. I would certainly say he is right and I support this way of explaining things. I'm a somewhat advanced Erlang user, and I enjoyed the article. I am not sure where you got that competition with Haskell aspect, but I don't think it was ever the point.