4 ms·

GWT users are doing ok. Yeah development is slow compared to when they had a bazillion engineers working on it during the Wave era... on the other hand, that's

GWT users are doing ok. Yeah development is slow compared to when they had a bazillion engineers working on it during the Wave era... on the other hand, that's when a lot of the overengineered crap got added. In the mean time, standard browser changes like source maps have really helped over the old days of browser plugins. GWT is a web presentation technology that has (so far) had a 12-year run. That's like a million dog years. Backbone is 8 years old, Ember is 6 years old, Angular1 was a flash in the pan... jQuery is the same age as GWT, but it's waning as well. I really don't think GWT devs have much to complain about. React developers should be so lucky in another ten years. Frontend technologies just don't have much shelf life.

bradleyjg 8y ago
> on the other hand, that's when a lot of the overengineered crap got added. People wrote stuff on top of each one of those “overengineered crap” pivots. It’s nice that a transpiler still sort-of exists but that’s of little use to people that built out products on the platform. And of course the back-compat story has always been terrible because google. Also it’s was a java framework pitched at java developers. Swing is still supported and applets were fully supported (not hived off to some moribund open source foundation) for more than twenty years.
- stickfigure 8y ago
  That overengineered crap still works? I mean, it was never a necessary part of gwt. There are a bunch of crappy react patterns you could use and we don't blame the core libray. Personally I think redux is overdue for a reckoning. I was doing gwt development in the wave era. I saw all the crazy new mvvpvmvwhatever stuff and just avoided it. App worked great. I don't use gwt today but I keep an eye on it every now and then. The transpiler is waaaaaay better now than it was in the wave era. The only thing missing is a modern widget framework. I don't expect gwt to make a major comeback, but it wouldn't surprise me too much of it did. It (still) does a few things far better than the current crop of JS frameworks.

bradleyjg 8y ago

> on the other hand, that's when a lot of the overengineered crap got added. People wrote stuff on top of each one of those “overengineered crap” pivots. It’s nice that a transpiler still sort-of exists but that’s of little use to people that built out products on the platform. And of course the back-compat story has always been terrible because google. Also it’s was a java framework pitched at java developers. Swing is still supported and applets were fully supported (not hived off to some moribund open source foundation) for more than twenty years.

stickfigure 8y ago
That overengineered crap still works? I mean, it was never a necessary part of gwt. There are a bunch of crappy react patterns you could use and we don't blame the core libray. Personally I think redux is overdue for a reckoning. I was doing gwt development in the wave era. I saw all the crazy new mvvpvmvwhatever stuff and just avoided it. App worked great. I don't use gwt today but I keep an eye on it every now and then. The transpiler is waaaaaay better now than it was in the wave era. The only thing missing is a modern widget framework. I don't expect gwt to make a major comeback, but it wouldn't surprise me too much of it did. It (still) does a few things far better than the current crop of JS frameworks.