I know absolute fuck-all about dart, but I do know that a programming language is just a tool. At the end of the day, a good programmer should be able to learn to use the best tool for the job, even if that tool resembles a swiss army knife.

It's apparent that Javascript has taken cues from nearly every other modern programming language at this point. The leaps and bounds being made with ES6 and ES7 are simply astounding. Of course, I have no problem seeing the development of languages like Dart, Coffeescript, and Typescript that compile to javascript, but I think there's an argument to be made for the reduced need of these. The development effort being poured into them has shaped javascript, but I think what many people are realizing is that the focus doesn't need to be on creating new languages that compile to Javascript, when it can be on advancing Javascript even further.

>I do know that a programming language is just a tool.

I'm probably going to sound very negative in saying this, but I _really_ hate it when people pull this line out like it means anything. Only in the most narrow, trite sense is a programming language "just a tool." They are the whole reason programmers exist. Language is the single most important development in human history, and computers have touched human life in irreversible and undeniably important ways.

Everything is just a tool, if you look at it the right way, and it takes a particular kind of pointlessness to opt to see the world like that.

Language is the thing that makes the genie grant your wish. If you wish with the wrong words, you get a billion dollar tombstone.

I just wonder, relatively, how big is the part of the ES6/7 driving community which were the people who hated on CoffeeScript because it required a compilation step (and now they love BabelJS). There will be things which you will always hate about JavaScript, visible, on the surface, and that will never go away. Compiled-to-js languages can hide these. This has been the best part of CoffeeScript, where it really shined, and this will carry over future compiled-to-js languages (PureScript, Elm etc.).

Unless it turns out that JS+Flow is actually the best balance between flexibility and safety and the world will reach "singularity".

I don't remember much of an objection to CoffeeScript on the grounds that it requires a compilation step.

For example, here was my statement advising Discourse to avoid CoffeeScript in 2013: https://meta.discourse.org/t/is-it-better-for-discourse-to-u...

> but I do know that a programming language is just a tool.

So I take it you write all your *nix programs in C?

> So I take it you write all your *nix programs in C?

That's the only sane answer if you have any intention of redistributing them.

> a good programmer should be able to learn to use the best tool for the job...

So you think JavaScript is the best tool for the job? I don't think so.