We wrote Application (medical) with GWT in 2010, and we still maintain it, occasionally adding new features. Once you figure out build step and magic incitatio

We wrote Application (medical) with GWT in 2010, and we still maintain it, occasionally adding new features. Once you figure out build step and magic incitation to make debugger work (and docment it), It's really not bad, and maintaining is easier then most other "older" codebases I come across. Old rubby/php/javascrip(jQuery/whatever) project is usually pain because they all use tons of external packages/libs that you have to update find new ones etc every time you take project off the shelf. With GWT and Java it just works, because we didn't use that many other libraries and Java libraries generally put a lot more effort in backwards compatibility. So no I would not start new projects in GWT anymore, but I think that current react projects will be a lot harder to maintain in 10 years, than GWT is.