Re:Angular Announces AngularDart
by Helianthus on Tuesday November 05, 2013 @09:23PM
(#6680122)
There's a bit of a chicken-egg problem with a project choosing Dart, in that Dart has to already be ubiquitous for it to even be an option.
What is the pathway for Dart adoption? Google puts it in Chrome. Sure. Dart programmers get to deploy to the Chrome browser, so they do some fun side projects and they run on Chrome only. Fine.
Show me how Dart can then move to every browser on every device.
Then show me how whatever hypothetical process you came up with doesn't apply to any other language that currently exists.
If we're going to put a new runtime in the browser, Dart isn't the only option.
> What is the pathway for Dart adoption?
dart2js: https://www.dartlang.org/docs/dart-up-and-running/contents/c...
How is that different from all the other languages out there that transpile to JavaScript?
Dart's one advantage is very fast development cycle if you use Dart VM in Dartium. No js compilation needed. Very well designed user APIs, Excellent modularity (with pub) and good editor support eliminates many opponents.
I have that with many other languages as well.
name one (especially skipping js translation step for development).
JavaScript
How are you driving it home besides just repeating it without any other supporting statements? Saying something 3 times doesn't make it truer.
> Dart will not replace javascript and will not be the native language of the web
Still don't get why it wouldn't. What is qualitatively different about DartVM vs v8. It could be 2-3 development cycles away from inclusion should Google decide to do it. What exactly code-wise is preventing that to happen?
> Unfortunately, my understanding is the dart2js process is horrifically inefficient, but that's no skin off my nose.)
Looking at their benchmarks their dart2js is not too far off v8 numbers. Now add types plus a nice IDE and I can see how a larger project might choose instead of JS.