3 ms·
Some of these criticisms are a bit unfair I think. History and back button support in GWT is very straightforward and trivial to implement. (http://code.google
by squidsoup 16y ago
Some of these criticisms are a bit unfair I think.
History and back button support in GWT is very straightforward and trivial to implement. (http://code.google.com/webtoolkit/doc/latest/DevGuideCodingBasicsHistory.html http://code.google.com/webtoolkit/doc/latest/DevGuideCodingB...)
The default compile cycle is long as GWT is compiling for multiple clients targets (and potentially localisations). You can speed this up a great deal by reducing compile permutations to 1 (http://code.google.com/p/google-web-toolkit-doc-1-5/wiki/FAQ_CompileOnePermutation http://code.google.com/p/google-web-toolkit-doc-1-5/wiki/FAQ...). You should probably also mention that you don't need to recompile in development mode.
- allertonm 16y agoSome of these criticisms are also true of all of the browser-side application frameworks - i.e SproutCore, Cappuccino etc. FWIW, the compile time is still pretty long even with one compile permutation - and even while developing there is sometimes a need do do this (for example, changes to serialized objects.)
- gthank 16y agoWhile there is a straightforward way to implement Back and History, the point is that traditional web dev technologies give it to you for free, so it's one more thing to think about. Compile time definitely gets better if you reduce the number of targets, but it still totally dominates most people's build times. Not needing to recompile in dev mode is definitely a big win.