>
To me this is like saying: "it's safe to defend Servo up to the point that it's faster single-threaded browser engines. Then Chrome and IE might fall behind in performing for web apps and then you will see how Servo will hurt the web ecosystem."
We are not implementing anything in Servo that does not have cross-vendor support and is on standards track. That's not the same as Dart.
I address this argument in the rest of my comment. Asm.js is not standards track as far as I know.
Actually let me post a thought experiment. Suppose that Dartium, instead of processing straight Dart source, processed a format that is like JS except that all the Dart is in JavaScript comments at the top of each Dart2JS-outputted function.
And suppose developers compiled their Dart to these JS-with-Dart-in-comments files, and distributed these on the web instead of Dart and JS as two separate files?
> At that point, how is Dart different than asm.js?
It's not guaranteed that the Dart VM and the dart2js-compiled code implement the same semantics. (And, in fact, they don't, by design—bignums operate differently in JS and the Dart VM, which could break sites in non-Chrome browsers.)
We are not implementing anything in Servo that does not have cross-vendor support and is on standards track. That's not the same as Dart.