With Google announcing at I/O 2012 that they were handing GWT over to a steering committee, it was a very confusing time for companies and developers who have invested in GWT throughout the years: Was GWT being abandoned? Would its progress be stalled?
It was nice to see that GWT was still being used within Google as evidenced in its two talks at Google I/O 2013.
Here’s a couple notes from the two talks:
Erik Kuefler (Google Wallet) talks about how Google uses the Model-View-Presenter (MVP) pattern with GWT.
GWT.create() instead of
GwtMockitoTestRunner can remove boilerplate GWT Mockito test code.
Start with the simplest solution that works. It’s not very hard to pull an interface out of the composite widget.
EventBus allows presenters to communicate without knowing about one another. This improves maintainability. Use methods for tightly coupled events. Use events for much higher level actions where
Google developers use the technologies they are comfortable with. Some use Dart, some use Python, Java... even GWT. There are still new internal projects that are started up using GWT. The most notable being Google Wallet and Ad Words.
All in all, it seems that GWT is not in danger of becoming obsolete.