[amoiseev]

I really like and appreciate how Seth clearly says that you will need to compile Dart to JS for the deployed apps. Thank you!

For a long time Dart community were awaiting when Dart VM will be finally built-in into Chrome, and it was one of the selling points we often heard - Dart will be natively executed by the browsers. However, I personally don't think it's a big deal. Even if tomorrow Chrome... even if all the browsers tomorrow will be shipped with Dart VM inside, we still will have to deploy compiled to JS version for the next 3-5 years (the same with ES6 btw).

Don't get me wrong, I am looking forward to see Chrome with Dart VM onboard, I just don't think it's critical for real business apps.

I also second @jenscow's opinion, compilation to JS is a feature that has some important advantages. For the last 1,5 year I've been working on a business web app written in Dart, it's deployed into production. Most of the time we use dev channel to get access to the latest features. For 1,5 year we never had an issue caused by compilation to JS. Actually 2 times we had issues reproducible only in JS version, but the errors were in our own code, had nothing to do with compilation process, regular race conditions that had higher chances to occur in JS.