Also, IANAL but I'm pretty sure you don't have to include a disclaimer to post on the internet. No one is going to rush out and buy Google stock based on your comments so there is no conflict of interest to what you wrote.
[regarding the disclaimer: I add it for two reasons. First, I have seen people accusing others of hiding their bias, so I prefer to state my affiliation explicitly. Second, if anybody wants to ask any Dart VM related questions and get response they know where to ask :-)]
/me ducks
:)
The Dart2js compiler could easily take advantage of asm.js additions, and generate javascript code that uses asm.js. If asm.js does take off, all it can do is help Dart generate faster running code.
Now, if we are talking about the DartVM, asm.js could be used as an argument not to include the DartVM in other browsers. But asm.js is still very much in it's infancy, so we really need to wait and see how it's adopted and how it progresses.
It would be very interesting to see a benchmark of emscripten/SomethingMonkey/asm.js vs emscripten/DartVM.
(Could also add emscripten/dart2js/V8 for giggles)
> That it is Dart isn't the story here; they don't even mention the Dart VM as a benefit for the switch.
Which I think is equating Dart with the VM? Then you say:
> They are switching because they like the language/ecosystem better.
That sounds to me like Dart is the story then. The language/ecosystem is Dart, isn't it? Can that be separated somehow?