gwt - Using <collapse-all-properties /> in production? -

from understanding, collapse-all-properties in gwt.xml, compiler produces 1 permutation browsers. , resulting files 15% 20% larger.

other increased file size, there other reasons why shouldn't use collapse-all-properties production?

for example, strip browser-dependent logic , css, causing app potentially work and/or differently when compiled default permutations?

in app, noticed 100kb size increase in cache.js , combined 50kb increase of deferredjs files collapse-all-properties.

but when combined gzip, code splitting , caching, benefit of smaller file size seems trivial compared significant fast compilation time , general ease of use.

got me wondering if use production.

there no reason can't use in production, aside reasons you've stated, , if expect of users arrive populated caches (app doesn't change often, , users bring app frequently), correct size point less meaningful. there still cost loading large js app memory , building of required methods, suspect not meaningful when compared loading 100kb server.

i don't believe collapse-all-properties disables split points (deferredjs files), or perhaps misunderstood , saying split points grew around 50kb.

if performance seems acceptable on lowest power machine expect users running app on, wouldn't concerned - no need optimize cases don't apply you.

i wary of additional locales (esp when new images used different locales), , 'form factor'-based properties (probably want keep mobile/tablets fast @ cost of build times). disabling unused browsers - while modern browsers converging on handful of required implementations, older browsers still around require code , additional ways handle features clientbundle (can't inline images data url). if able remove browsers application, may recover large amount of increase seeing.

there has been discussion in general gwt roadmap of removing permutations entirely, since largely holdover time when each browser behaved differently others, while still have ie8/9 support, difficult. future modern-browser-only gwt leave permutations behind entirely, , encourage solving problems locales in different way.