All of this will change when the virtual machine that runs our DART code natively is deployed and supported by most popular browsers, in particular Google Chrome will support it natively.
Previously we used FROG to compile DART to JS. From now we will use a new module called dart2js.
The DART team is working hard on the optimizations so that in future this new module will be faster and more efficient than FROG and, above all, it’ll generate more efficient code.
I leave the official note.
It’s time to say goodbye to frog. Within the next two weeks, we will
be deprecating frog and removing it from the SDK and the editor.
Starting early next week, we will be updating our build bots
(http://buildbot.dartlang.org/) to spend even more time testing
dart2js and less time testing frog. Once everything is in good shape
and we’re happy with our test coverage, we will pull the plug on frog
posted on our progress.
If you haven’t updated to dart2js yet – now would be a fantastic time
to do so. It already ships as part of the SDK and the editor and it is
easy to use:
Usage: dart2js [options] dartfile
-o<file> Generate the output into <file>.
-c Insert runtime type checks and enable assertions (checked mode).
-h Display this message (add -v for information about all options).
As always, we really appreciate feedback and bug reports and we will
do our best to deal with issues quickly.