I ran tests on iPhone and Android 2.0 SDK with Showcase and I didn't see any significant different in startup times over wifi (3g/3dge may be a different story), so the latency improvement really only shows up in degenerate test cases where all functions are polymorphic, small and/or empty, so that parsing function decl headers becomes dominant. However, a 2-6% size reduction is nothing to sniff at, so I'd still say it's worth it.
Onto the String eval idea. :) -Ray On Fri, Oct 30, 2009 at 10:08 PM, Bruce Johnson <br...@google.com> wrote: > > yep, and all of them should be per-perm > > On Saturday, October 31, 2009, Ray Cromwell <cromwell...@gmail.com> wrote: > > Maybe it would make sense to move properties which the compiler relies on > into a special CompilerFlags.gwt.xml module, then if you want to change > class meta data, class cast checking, aggressive optimization, or stack > info, there'd be one centralized place to look at and document all the > flags.? > > > > -Ray > > > > On Fri, Oct 30, 2009 at 9:31 PM, Bruce Johnson <br...@google.com> wrote: > > > > > > I wish we could wrap that all up in a simpler-to-understand package. > > But a good article would make it at least bearable. > > > > On Saturday, October 31, 2009, Ray Cromwell <cromwell...@gmail.com> > wrote: > >> > >> > >> On Fri, Oct 30, 2009 at 8:24 PM, Bruce Johnson <br...@google.com> > wrote: > >> > >> > >> In terms of design, I think this would actually be best as a > permutation-specific conditional deferred binding property that the compiler > is sensitive to (that was a mouthful), so that it would be possible to let > app developers control how many stack trace-enabled users there are, in the > same way they can control how many users get the expensive emulated stack > traces on IE. I would guess something like <= 10% would need stack traces > enabled to still get good stats. > >> > >> Perhaps we can think of it as a tri-state variable: strip stack info, > browser supplied stack info, emulated stack info. Choose per permutation. > >> -Ray > >> > >> > >> > >> > >> > >> > >> > >> > >> > > >> > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---