During the last three years, I was involved in many GWT based applications development.
I should admit that it was funny and really challenging tasks. But, after three years doing the same things, I feel the need to make some critics about the GWT:
- It isn't the ideal technology choice to do prototyping : making even sample application working take time and effort (if we want to follow GWT development best practices).
- Slow development cycle:
- even with using a all the possible build optimization(draft compilation, generate less code permutation, .. ) the build still very slow for a small application : around one minute.
- even when using the development mode facilities(using embedded Jetty), testing a small change of the source code take long time(very common in case of junior developer)
- The learning curve is really important for juniors developers. In fact, lot of design patterns used to build an industrialized large scale application(MVP, Activity and Place ..), which isn't sample for a junior JAVA or web developer.
- The biggest added value of GWT is to develop one time and use for all the web browser, BUT it's really romantic vision. In the reality the generated java script is not really cross browser compatible (as promised).
- Documentation isn't the biggest advantage of GWT, the official documentation still poor (compared to the maturity of the project 2.5 version out..).
Finally, I'll be happy to receive your comments!