On: “We have decided not to integrate the Dart VM into...

[have_humility]

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

If that's the metric we're applying, Dart fares no better...

[spankalee → have_humility]

How so? You can use Dart today and yesterday and tomorrow.

[spankalee → spankalee]

wycats: IE 10 and up, Safari 6 and up, Chrome, FF, Opera, last 2 versions.

[wycats → spankalee]

In what browser?

[wstrange → wycats]

Chrome, Firefox, Safari and even IE!

All via dart2js

[nailer → wstrange]

Sure but you can also use es7 today (which I did).

[axlprose → nailer]

Yes, and even compared to ES7, Dart still fares rather well. Most people that doubt this seem to not have actually tried the Dart workflow and core libraries. The productivity gain from those two features alone makes it compelling against all other compile-to-js options, because what it brings to the table isn't just a fancy language with nicer syntax+semantics.

[nailer → axlprose]

The dart std lib, at least the DOM manipulation bits, are indeed nice.

OTOH: JS has the largest module system of any programming language ever, which also tends to make it pretty productive.