3 ms·
Saying Dart needs Microsoft adoption is like saying CoffeeScript or GWT needs Microsoft adoption. They all allow JS compilation and the ability to use JS and be
by kodablah 15y ago
Saying Dart needs Microsoft adoption is like saying CoffeeScript or GWT needs Microsoft adoption. They all allow JS compilation and the ability to use JS and be called from JS. Google will likely make an IE extension to run Dart natively anyways.
- viggity 15y agoIf it requires my users on a public site to install an extension, I'm not going to use it. case. closed.
- kodablah 15y agoIt wont. No legitimate developer would replace JS with it if that requirement existed.
- eCa 15y agoWhat he said was that Dart will compile into JS. Natively run Dart will (otherwise, what's the point) than the JS it can be compiled into. What I forsee is some kind of conditional that will allow Chrome to run the Dart code, and other browser get served the compiled-into-JS. Demanding an extension installation is a no-go.
- azakai 15y ago> Saying Dart needs Microsoft adoption is like saying CoffeeScript or GWT needs Microsoft adoption. They all allow JS compilation and the ability to use JS and be called from JS. I'm not sure that is the case, because of the native Dart VM. CoffeeScript compiles very straightforwardly into JS, with similar performance to normal JS. But Dart is significantly different, and the Dart VM could be faster than Dart-compiled-to-JS, both because (1) The Dart VM will be optimized for Dart in new ways, and (2) It isn't clear that Dart code will be extremely efficient when compiled to JS. So CoffeeScript adoption needs no support from browser vendors, but Dart, if it is to fulfill its goal of being fast, might need the Dart VM. And that does need browser vendor support.