Open vegegoku opened 5 years ago
I think that using the same programming language for front- and backend is always a good stuff. This makes it much easier to share code between client and server. This was e.g one of the main reason why we decided to go with GWT. If you go with TypeScript or JavaScript on the client side sharing code can be difficult if you don't have NodeJS in the backend.
Maintainability is a good point! Also typesafety and the great toolchain around Java. There are a lot of potential points in the docs which maybe not up to date anymore: http://www.gwtproject.org/makinggwtbetter.html (introduction)
We need to prepare a small paragraph talking about gwt in general : Some bullets to point out could be
Basically: Modern, Performant, Stable - By : Adrien Baron
also could point out to the property system, allowing permutations for changes as necessary, for locales or browser differences or form-factors - By : Colin
also Maintainability.
List the strength of GWT