>>10
async is way easier when your language was designed for it, when all your libraries support it default, and when streams and events are language primitives.
>>3
argument by evidence
>>9
my biggest problem with erlang is that basic shit like text processing doesn't work, and the whole architecture is built for a ton of upfront design for scaling.
If you know that your software is going to have to run across the world and satelites and never fail, then erlang is a great choice.
but 99% of projects don't need to scale. stuff like node and python succeed in web programming because you can just dive right in and get productive asap. You don't have to waste time worrying about a problem you don't have.
Once you finally have to worry about scaling, you can probably start hiring more people anyway.