That section doesn't touch on "To paraphrase: we have a powerful compiler, let it do work for you, you can't get that from <insert latest JS lib here>." It talks about the fact the mere presence of a class in the compile classpath changes the output, and the difficulty of tracking dependencies: add an "implements X" to a class and a totally different part of the application could "need" to be recompiled (re-generated), just because it references "X" (but not the class that was changed). This is not about *whether* to use the compiler but rather how to use it efficiently.
-- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
