The following webpage says that GWT is complex and incomplete solution, which is best for very smart people and proposes a simple and complete Ajax GUI Classes for not so smart people: http://www.cbsdf.com/ps_blog/why-other-frameworks.htm So many pages of the article certainly shows that GWT is more hard to learn.
Software developers have a number of different Ajax toolkits and libraries at their disposal. The challenge is to settle on a "flavor" that best matches your style, skills, and requirements. I also favor Prototype, for instance. The reason I like what I've seen in the GWT (which is still in beta) is that 1) I use Java; 2) the GWT allows me to design an Ajax application using object-oriented design and UML drawings, a well-organized approach to software development; 3) the RPC mechanism GWT uses is servlet-based, and I use servlet containers for server-side processing; 4) the IDE I use, IntelliJ IDEA, is incorporating GWT support.
A JavaScript programmer, on the other hand, might just stick with the Dojo toolkit (http://dojotoolkit.org/) or Prototype. A user-interface designer may simply want to plug finished components into their templates. It all depends on your preferences.
Previous Message
