On Fri, Jun 19, 2009 at 8:23 AM, Lex Spoon<[email protected]> wrote: > The main tradeoffs I see are that the files version integrates well > with existing tools and IDEs. No matter what build tool you use, you > should be able to get a fast incremental build by using the files > version. On the flip side, for people that manage to get set up with > the process version and keep their process running, the refresh speed > should be faster than with the files version, because it won't be > doing any serialization.
GWT can't be all things to all people all the time, but this seems like an opportunity to "do both". Couldn't the files-on-disk be a serialization of the data-in-memory? Then the compiler could use the long-running process as a cache--if the process is there, use it, if not, start the process by deserializing something from the disk. You get both for "free", no? Ian --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
