There is some decent justification in there, but I think the generic question, in a lot of questions is:
Why did I choose to build X with Y?
The generic answer is usually:
Because it is what I know.
The extended answer may include particular features of the language or environment or it may include the support provided by a particular cloud infrastructure.
As an example, the stuff I am personally working on now, I mostly use Python because I know it well and the ecosystem for webapps is pretty mature. 7 or so years ago, Python (in particular) mod python wasn't even close to modphp, so I went with PHP. Today, if I was adamant about building on Azure, I'd choose NodeJS (thus JavaScript) or C# because they are first class citizens of the platform.
In other words, choice of language can take on many facets. Good to see PERL mentioned again.
There are always tradeoffs, but sometimes you can find "the best tool for the job". And that may or may not be the tool that you know. You gotta be flexible and open to learn other tools that may suit the situation better.
In the post I don't bash any other languages at all. In fact, I encourage people to learn other languages too. At the end of the day, it'll help you evolve your thinking process and extend your skill set.
Not saying you bashed languages, but made a good argument for PERL. And the points were good and provided substance. Which, personally, I find useful and will likely guide me to look into things I may not know or revisit something I don't know. PERL might be the exception.
What I liked about the post - it didn't focus on hype, like that around NodeJS (it's badass rock star tech); additionally it brought up a language no so en vogue.
Why did I choose to build X with Y?
The generic answer is usually:
Because it is what I know.
The extended answer may include particular features of the language or environment or it may include the support provided by a particular cloud infrastructure.
As an example, the stuff I am personally working on now, I mostly use Python because I know it well and the ecosystem for webapps is pretty mature. 7 or so years ago, Python (in particular) mod python wasn't even close to modphp, so I went with PHP. Today, if I was adamant about building on Azure, I'd choose NodeJS (thus JavaScript) or C# because they are first class citizens of the platform.
In other words, choice of language can take on many facets. Good to see PERL mentioned again.