As someone who has been learning Erlang for a few months now, I mostly agree with the article. The only statement that rubbed me the wrong way was: Many Erlang

As someone who has been learning Erlang for a few months now, I mostly agree with the article. The only statement that rubbed me the wrong way was: Many Erlang programs are running in companies with no open-source policy as well - don’t expect the programmers of those systems to even be able to talk about what they do. It is a competitive advantage to keep the mouth shut. In fact, I see the shut mouths as a disadvantage in some cases: coming from the Ruby/Rails world, it was a shock for me to not find an open-source library, yet find a request for it back in 2000. Further investigation revealed some well-known authors having worked with the closed-source version. What we'll probably do is take the equivalent Ruby library, and make it work through Erlectricity.