This is very useful feedback. We're planning on making the frog
integration simpler which may help alleviate this problem. Right now
the compiler runs as a background service (on top of dart.exe on
Windows) which means that if something goes wrong you may be stuck
with a lingering service process that doesn't really work anymore. As
a first step, we're planning on essentially restarting the service for
all compilations and use the compiler more as a command-line tool than
a service.
> As a general thing - it does seem that when I hit the save button (or
> Ctrl+S) which I do out of habit after nearly every edit, this invokes the
> builder before the save actually happens. It would be good if we could be
> sure that the save happened so that even if the builder crashes, it saves
> the work.
Yeah -- people tend to assume that Ctrl+S actually saves their work.
We should fix this :-)
Cheers,
Kasper