> But in the end it's still javascript which makes it hard to create native and mobile builds. It's not "still JavaScript." Dart has its own VM and own librar

> But in the end it's still javascript which makes it hard to create native and mobile builds. It's not "still JavaScript." Dart has its own VM and own libraries. Yes, you end up deploying to JavaScript in most scenarios, but Dart is its own platform which can live on its own in the server context and when the Dart VM is integrated with Chrome, on the client side too. I know what you meant, but the way you worded it does a disservice to Dart, making it sound like another CoffeeScript.