4 ms·
Because: # JS has shown surprising legs when it comes to performance improvements # For a competitor to become popular it’d have to persuade every browser man
by robin_reala 12y ago
Because:
# JS has shown surprising legs when it comes to performance improvements
# For a competitor to become popular it’d have to persuade every browser manufacturer to implement it
# Once implemented it’d have to wait for multiple years for devices in the market to implement it
# Older devices are slower devices, so having a compiles-to-JS version that lags in performance for older devices isn’t tenable either.
Basically, it makes more sense to increase the local maximum than any other path.
- tosh 12y ago> # For a competitor to become popular it’d have to persuade every browser manufacturer to implement it IMHO this is a misconception. Dart compiles to JavaScript with decent performance of the generated code. In some cases even faster than comparable hand-written JavaScript (see: http://dartlang.org/performance http://dartlang.org/performance). JavaScript engines getting faster also means that Dart code compiled to JavaScript is getting faster. It is a win-win scenario. Even if other browser vendors won't ship a Dart VM tomorrow the situations is pretty awesome performance wise. Once Chrome ships a Dart VM a huge user base gets even better and more predictable performance characteristics than would be possible in JavaScript which is incredible but I don't see the browser vendor support/performance angle as a real show-stopper for Dart. You don't give anything up when you use Dart, you can still call JavaScript libs if you need to (e.g. we do use PubNub.js at https://www.blossom.io https://www.blossom.io and we use it from Dart without any problems).