From GWT to greener pastures
We had a few issues:
- making changes during development meant waiting for 20 seconds to see the effect – GWT has to reload the code in “hosted mode”
- the incubator library did not support later versions of GWT, we were locked in unless we wanted to convert all table code
- future support for GWT is questionable (GWT team now working on Dart)
- it is a bit niche, hard to find questions and answers compared to other frameworks
- GWT RPC is not human readable nor sane
At some point we decided that we should make an effort to make GWT upgradeable, which meant replacing all the tables – which actually meant rewriting the entire application. Given some of the problems mentioned above would not be alleviated by upgrading, I decided to write a report that weighed the pros and cons of staying with GWT and presented this to our team. Based on this report we decided to plan how we could migrate away from GWT to a less niche web framework collection.
The new framework consists of a collection of libraries such as: backbone, asm, jquery, mustache – libraries that: had substantial documentation compared to alternatives, community support and considered generally accepted within the web development community.