[Crabber]

I think the problem is that javascript has stopped being one language of many and has become the language.

There are hundreds of thousands of developers now who only know javascript. They have no perception of the parts of javascript that are badly designed because they don't know any other language. They think that computers taking 500ms to render a webpage is just how slow computers are because that's how it is with javascript. They think desktop applications that use 400MB of memory on startup are normal.

People no longer weigh up the pros and cons of javascript and decide it is the best option for a certain project. Javascript is all they know, and it shapes their entire view of programming.

[jdlshore]

Oh, come on. JavaScript doesn’t mean pages take 500ms to load. On my Node.js-powered server [1], pages take a handful of ms, and they only take that long because I’m doing a lot of sophisticated content management.

JavaScript has got some rough spots, but it’s a fine language these days, with a nice multi paradigm support.

[1] jamesshore.com or letscodejavascript.com — they both run on the same servers.

[cercatrova]

I'm pretty sure they're talking about client side JS bundles, not a NodeJS server that renders HTML.

[jdlshore]

Heh, good point. It’s still a silly language-wars comment, but it makes more sense.

[AlchemistCamp]

The kinds of devs who don’t regularly learn new languages are generally the ones you don’t want to hire.

[herbst]

Learning new languages is a different thing than crunching into the next JavaScript fud.

[AlchemistCamp]

The great thing about learning more languages is that you tend to gain new skills to take back to your old projects. This is especially true for languages meaningfully different than those you know.

The same can be true of frameworks, databases and other tools.