I think the goal was to implement all of those kind of optimizations using
the javascript closure compiler.. so dead code elimination and shrinking
and code-splitting would all be done by the closure compiler.
I'd guess the GWT code would remain similar, and the output javascript
would use
My understanding is that you can pass in parameters (for each permutation)
that the compiler/linker can see as constants so optimise away.
I think this is getting less focus in the belief that browsers are getting
less quirky and that a mono-culture of GWT is not the way to go so it needs
to
when GWT 3 is more targeted to js libs/GUIs, then does it mean, that we
will lose all benefits, like code-splitting, different permutations for
languages/browsers, etc.?
i.e. as I understand it, even a Polymer component must include all the
bloated css/js-quirks for different browsers, right?
