Added this to the Later milestone.

Removed this from the Later milestone.

Added MaybeStale label.

Added this to the M2 milestone.

Removed Type-Enhancement label.
Added Type-Defect label.

Removed this from the M2 milestone.
Added this to the Later milestone.
Removed MaybeStale label.
Added AssumedStale label.

This is not stale, this is a real issue. Talking to our internal customers, they are asking for edit/reload cycles with dart2js to approach edit/reload cycles for Dartium.

I admit "much faster" is undefined, but I didn't want to throw a number down.

Can we keep this open so we have something to reference? If it helps I can arrange a meeting with our internal customers to get more specifics.

Added Triaged label.

This comment was originally written by beatg...@gmail.com

Just my 2 cents.

For me, dart2js takes about 8 seconds on a file < 100 lines which imports dart:html, dart:json and dart:uri. My resulting JS files are around 8000 lines (< 300k). I currently have two pages, so two dart files takes 16 seconds, which is a little long for debugging. If possible, I would like to see this build in less than 3 seconds.

This should probably be a separate issue, but it would also be nice for dart2js to refuse to build if the file hasn't changed.

Hi beatgammit, have you tried to minify the output? See http://blog.sethladd.com/2013/03/i-shrunk-my-dart-to-js-code-by-11x-and.html for tips for turning on minification. Hope that helps!

This comment was originally written by beatgammit...@gmail.com

Minifying isn't the problem, which I'll do when I deploy. The problem is how long it takes to compile to JS.

Added TriageForM5 label.

Removed TriageForM5 label.

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

Hi Peter,

Is there a bug for "incremental compilation" ? I think I should mark this a dupe of that issue.

cc @peter-ahe-google.

Removed Oldschool-Milestone-Later label.

Let's make this the bug for "incremental compilation".

I'll try to keep this bug updated with progress, but somehow it is more natural to post about my progress on Google+. See https://plus.google.com/u/0/+PetervonderAh%C3%A9/posts/dXix8pdbotE

Removed Type-Defect label.
Added Type-Enhancement, Started labels.

This comment was originally written by @Emasoft

I think that the real issue here is that there are still problems generating js code that works across all browsers.
The team should be implement polyfills to flatten all the differences and bugs of the various browsers. Dart should offer the same advantage of GWT: browser abstraction. And now with the Polyfills becoming a standard, the Dart team should make the differences between the browsers disappear and make the Dart code run as it were always running on an ideal browsers with the latest W3C specifications even if they are not implemented yet.
Just take all the features listed as missing in http://caniuse.com and write a polyfill for it. Only then the programmers can work with Dart without being slowed down by a forced Dart2javascript additional compilation.
We are entering in the "Polyfill Era" for the web, when the incompatibilities between the browsers that haunted the world are finally going to disappear. Dart should be the first development platform born for the new web.

@fmuaddib, I think you're talking about a different feature request, and I'd encourage you to file a new bug report for that. Making JavaScript compilation fast is a worthy goal in itself.

This comment was originally written by @Emasoft

@ahe : I just opened a more specific issue ( issue #20346 ). Thank you.
https://code.google.com/p/dart/issues/detail?id=20346

So uh, @vsmenon do we want to close this as "DDC"? :)

sgtm