On Mon, Apr 15, 2013 at 8:48 PM, Ray Cromwell <[email protected]>wrote:
> Another downside of DevMode maintenance is all the hacks needed in the > codebase around isScript()/@GwtScriptOnly and other magic JVM stuff. > Many of those hacks are there for both performance and debugging (ie, where the JS version is a more complicated implementation to get decent performance when compiled to JS), and not all of them are just because of slow boundary crossings. So, I suspect by doing away with them you would simply make everything slower. > There are still lingering bugs in HostedModeClassRewriter around > SingleJsoImpls and generics. I agree that there is nothing that works as > smoothly and JVM roundtripping, and even if an incremental SDM mode could > have equal or superior reload performance, there is still the issue of IDE > integration. > > On the other hand, for debugging integration with JS, and using GWT code > in contexts like Chrome extensions, SDM is a lot nicer. It's also way nicer > for stuff like games, where the invocation overhead becomes large for stuff > like canvas and webgl. > So it sounds like they each have their place. -- John A. Tamplin -- -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "Google Web Toolkit Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
