Addressing Misconceptions about Google Web Toolkit
It appears that many people, including decision makers, are not fully aware of important GWT abilities and limitations. Many features in recent releases of GWT and related projects can be real game changers for the developers and for the end users. Here I am going to address common misconceptions and provide solutions to common issues.
"GWT does not support browser history (back button, bookmarkable URLs)"
That was never true, though in earlier versions of GWT this was not so easy to manage. GWT provides access to the browser history using static methods in its History class, which is sort of fine for small applications. In GWT 2.1, Activities and Places were introduced, letting you programatically associate history tokens with your activities. A cleaner solution in my opinion is provided by the GWT-Platform project - an MVP framework which, among other things, lets you use annotations to associate URL tokens with your presenter, and also lets you easily create and parse URL tokens with parameters.
"A large GWT application would take a long time to download, so we would be better off using HTML pages"
"GWT is awsome! I will use it for every web project"
"GWT is not crawlable"
As Ajax applications become more popular, the need came for search engines to be able to crawl them, even if they are a single-page site. To make your application crawlable, its history tokens should start with "!", as described here.
As you see, many of the concerns that were true in the past have been addressed over time. Whenever you think something is missing in GWT you should google for it, most likely there is a solution in GWT or a third-party library.