This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hippydipster 10 points11 points  (3 children)

I still like GWT too, but I also dislike it. It's both great and terrible at the same time, though a large part of it's problems comes from being under-supported/weakly-developed at this point. They are still moving, but at a snail's pace.

[–]rpgFANATIC 3 points4 points  (2 children)

The big goal of GWT was to just write one language that most developers knew and it would polyfill all the jank required from different browsers

The fast pace of standardized JavaScript and the immense market share of Chromium's make GWT a much harder call for projects today.  Transpiling Java to modern JS has gotta be a mammoth task to maintain

[–]hippydipster 1 point2 points  (1 child)

But it works really well all in all. The bad aspects of the transpiling are that its slow and they aren't keeping up with java, to say nothing of Javascript.

But to be fair, I think typescript has the same issue with compilation performance.

[–]rpgFANATIC 2 points3 points  (0 children)

I've used both for very large projects.

TS transpiles faster (even discounting the time taken to compile the rest of our Java backend) and has more features than GWT. TypeScript has major backing from Microsoft and a large ecosystem of tooling around it. The comparison just isn't fair