[jmspring]

Funny how so much of todays "wars" center around Javascript at the front end or bringing it down into lower levels/the back end -- nodes, etc. I like to refer to it as the era of the "Webscale Wars"...in homage to the awesome Mongo/Node webscale/rockstar bad ass tech videos.

Missing in a lot of this is that many of these tools that allow for "X is OMFG so amazingly awesome and webscale and ..." is years of churn, some progress towards "standards", and a foundation in lower level languages that enable these technologies.

In the gold rush, those that sold the shovels, the jeans, and the food made the bigger, less riskier dollar. In the coming generational war, as you posit, if it were to occur, having a toolset that includes things beyond Javascript will be key. In seriousness, especially on the nodejs front, any serious application you develop will run into bottle necks...in nearly 99% of those cases, just javascript isn't going to get you out of them. Breadth in experience, tooling, and mindset has it's advantages.

[hackula1]

As someone who would whole heartedly identify himself as a node dev, the most valuable code I write is in python. Node and JS in general is great for "glue code", but at the end of the day, most of us need to have something to actually glue together. Dependencies play a huge role in this. In my case, python has far better support for GIS, analytics, and machine learning. For 90% of us, scaling is not really ever an issue. Typically the real question is, does language X have library support for Y functionality.