4 ms·
GWT is still being maintained, and I hear GWT 3.0 is on they way with a lot of great features. The problem with GWT is that newer Google-associated projects ar
by spankalee 12y ago
GWT is still being maintained, and I hear GWT 3.0 is on they way with a lot of great features.
The problem with GWT is that newer Google-associated projects are perceived by some people as better (and the comparison is not always apt): Web Components, Polymer, Dart, Angular, etc.
But that doesn't somehow make GWT any _worse_ than it was before, and it's still improving. The compiler is faster, they're adding Java 8 features like lambdas, the JS interop is better, they're tracking web APIs closer, and I think they have a even plan for web components integration.
I used to use GWT extensively, and I would be one of the ones to argue that it's approach was great at one time, and probably a bit outdated now, but it's not abandoned and it's evolving to fit better with today's modern browsers. I might not choose it today, but I wouldn't regret choosing it a few years back, or be in a huge rush to move off of it if I had a large codebase.
- shangxiao 12y agoIt's funny because although I regret using it to deliver products, I don't regret having been exposed to it as a developer. I learnt a lot about how to build well structured front end code by using it. I still believe it's doomed though just because I don't believe they can match the pace of the JS world.