When not to use Google Web Toolkit?

Question

I'm considering use of GWT on a major in-house web app development project, namely it's major advantage in my eyes is the cross-compilation to Javascript which would (at least theoretically) help my team reduce the size of tech stack by one.

However, having been burnt before (like most devs), I would like to hear from programmers who did actually use it on any problems with GWT which would hamper, or limit, it's use within a certain problem domain.

When do you not recommend using GWT, and why?

Answer 1

I didn't read all the comments in the link that Jamshid provided, so this might have been addressed there...

If you want to build something closer to a traditional web app (i.e., web 1.0) that is centered around the concept of pages and forms being submitted, then GWT will be a hindrance. However, if you want to build something with a richer interface that's more like a desktop app (i.e., web 2.0), then I've found GWT to be nifty for a couple reasons:

• I can write and test most of my code in Java, which I know much better than HTML and Javascript.
• I don't have to spend much time worrying about cross-browser support.

That said, GWT isn't perfect. Trying to integrate with third-party Javascript libraries is hardly pain free, and getting it to work how I wanted with maven and eclipse gave me a few headaches. If you do go with GWT, I highly recommend watching this presentation - Google Web Toolkit Architecture: Best Practices For Architecting Your GWT App.