81 plus ones
Shared publicly•View activity
View 6 previous comments
- The tentative plan is to finish getting incremental compiles in SuperDevMode rock solid, then spend 1-2 weeks in release candidate testing, then release. So the actual release date will depend on how things go. I'm guessing that we will deem incremental compiles solid in about 1-2 weeks from now. But it all depends.Sep 30, 2014
- Does this work on file save or only on browser refresh ?
We use GWT for non browser based projets too (for example in NodeJS)Sep 30, 2014
- At the moment SuperDevMode supports 2 two ways of triggering compiles (depending on launch flags): either trigger a compile via hitting a recompile URL (bookmarklet) or else recompile on page reload.
We are talking about starting to do live file change detection and immediate recompile but we haven't settled any of those plans. It would definitely be nice to reload and already have the new compiled result ready and waiting.Sep 30, 2014
- What Jens' said is correct but I want to add to it a little bit. The incremental compile process is facilitated by a "MinimalRebuildCache" object that SuperDevMode persists from one compile to the next. At some point we will also persist this cache object to disk and reuse on next process launch, that way even a brand new launch will get some significant performance gains. But there's no timeline on that change. We're still in the process of heavy beta testing for the purpose of flushing out all the bugs from the current implementation.Sep 30, 2014
- Compilation of wars for production binderies will still be about the same as 2.6?Sep 30, 2014
- Yes, production compiles will be about the same as 2.6. This change is an improvement in SuperDevMode compiles and somewhat relies on disabling of optimization and codesplitting, which is not an option for production compiles. So it's an improvement in developer productivity but not an improvement in production compile time.Sep 30, 2014
Add a comment...