> 1. Difficult to develop or debug without custom IDE plug ins. With Google cutting back on their investment, not clear how well those plug ins will be maintain

> 1. Difficult to develop or debug without custom IDE plug ins. With Google cutting back on their investment, not clear how well those plug ins will be maintained in the future. Interesting, I'm just using IntelliJ IDEA‎ and their GWT plugin. What are they using? > 2. Awkward to work with Javascript libraries, at least compared to all Javascript development. Fair enough, it does take some getting used to it. > 3. Sometimes hard to predict exactly what Javascript will be emitted for specific Java code. I'm not sure why this matters? I thought that's the idea when you add another abstraction layer. > 4. Remembering the rules for what Java code can or cannot be compiled by the GWT compiler. Oh I think I get it now, they haven't migrated to Super Dev Mode yet. That way it no longer requires a browser plugin (the old devmode), and the code is just JS + sourcemaps. And if you use code that can't be compiled, you know straight away, not just when doing a production compile. > 5. A lot of indirection. The event model has definite benefits, but it also seems to make it very hard to figure out what the program will do by just navigating the code. I don't agree with this, but I'm probably biased as a Java guy. > 6. Difficult to find developers willing and able to work on a GWT code base. I'm available :-P But being serious, thank you for the write-up, you do have some good points.