The funny thing is, most of the people extolling the virtues of JavaScript here and in the comments on the article are referring to themselves as gurus/ninjas/rockstars/badasses/demigods with worrying frequency.
Roles where demand exceeds supply often start receiving a lot of hype and faux-respect in a effort to attract people to bridge the gap. As soon as the gap is bridged adequately, people will go back to seeing JavaScript "ninjas" as the code-twiddlers they really are. It's similar to how soldiers are patriots/defenders/heroes when someone is required to dive on a grenade, but "grunts" otherwise.
The sad thing is, people let it go to their heads. Another sad thing is how easily these JavaScript developer types are swayed compared to other professions. I mean, who really takes pride in being called a "ninja", besides 12 year old boys?
Is it just me, or does the article and about 90% of the comments seem like extreme navel gazing? You could paraphrase most of them simply as "Look at me, I'm a JS badass/ninja/guru/rockstar and in very high demand -- but I'm not full of myself, honest!".
"it allows you to model a problem domain in real-world terms"
Which is exactly the kind of specious, guesswork solution one would expect from non-practising management types and committees. In most situations, the contortions and indirection involved in this kind of approach usually outweigh any real benefits.