On Thursday, July 5, 2012 5:37:08 AM UTC+2, Magno Machado wrote:
I was impressed to see the results achieved on gwt 2.5 by combining the gwt compiler and closure compiler.
Well, I always thought there's nothing that closure could do that the gwt compiler couldn't already do, because gwtc have a lot more information about the source than closure compiler.
Yes and no: Closure has "static typing" via JSDoc annotations, and uses the same kind of monolithic compilation (i.e. I know everything about what will run, so I know what is never used that I can remove).
So I wonder what kind of optimizations closure is doing that were not already done by the gwt compiler?
One small optimization I've read on the Closure Compiler group that I know GWT doesn't do: ["ab", "cd", "ef", "ghij"] is compiled into "ab,cd,ef,ghij".split(",") !
(it's more in terms of perfs than in code size I guess though).
I don't know about the other differences.