“We have decided not to integrate the Dart VM into Chrome”

Re:“We have decided not to integrate the Dart VM into Chrome” by xixixao on Wednesday March 25, 2015 @07:10PM (#9266691)

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".

[ Parent | on HN ]

Re:“We have decided not to integrate the Dart VM into Chrome” by wycats on Thursday March 26, 2015 @08:22AM (#9268993)

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...

[ Parent | on HN ]