Nearing the end of 2009 I switched jobs to a new location, where I was tasked with building a new web application. The weapons of choice was Google’s, very new to the time, GWT 2.0.
GWT emphasizes reusable, efficient solutions to recurring Ajax challenges, namely asynchronous remote procedure calls, history management, bookmarking, internationalization and cross-browser portability.
In my two years work with GWT I can say that these are the pros and cons with the platform:
- Very manageable code, hierarchical and modular
- Splitting the code to Widgets produces highly reusable code
- MVP design for web apps is perfect in the way that the UI is just as important as the code behind it
- Medium-high overhead, requires time to get used to and work fast
- Can become a source of over engineering
- Some are frustrated by the amount of files per functionality
In the next post I will got through my implementation of MVP and explain the reasoning for it, you can take it as is, just the parts that you like, or completely reject it (but if you do, please comment why).