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

Re:“We have decided not to integrate the Dart VM into Chrome” by bhouston on Wednesday March 25, 2015 @03:35PM (#9265372)

> Sorry, using the present tense for things that will be in browsers years later (hopefully) is a common practice that's an issue with me. Let's stick with what people can actually use today.

ES7 async/wait is available now via the ES7 polyfill Babel.js: http://babeljs.io/

There are a ton of polyfills available right now for ES6/ES7 features: http://kangax.github.io/compat-table/es7/

BTW I also think that the current state of aggressive polyfills is also influenced by Dart's compile to JS functionality. :)

[ Parent | on HN ]

Re:“We have decided not to integrate the Dart VM into Chrome” by skybrian on Wednesday March 25, 2015 @04:28PM (#9265701)

Comparing Babel.js to dart2js is fair. I'd be interested in hearing more about about how well it works in practice from people who use Babel.js for large apps. (Also, how does it compare to Typescript?)

[ Parent | on HN ]

Re:“We have decided not to integrate the Dart VM into Chrome” by spellboots on Wednesday March 25, 2015 @08:41PM (#9267069)

Anyone creating a new Ember.js application today is using babel by default. It works very well in my experience. I haven't used typescript however.

[ Parent | on HN ]

Re:“We have decided not to integrate the Dart VM into Chrome” by bhouston on Wednesday March 25, 2015 @08:54PM (#9267123)

I think with time Typescript and Babel.js are to be merged, if you through in Strong Script to the mix I guess you have the future of JavaScript.

[ Parent | on HN ]