Skip to content

Instantly share code, notes, and snippets.

@AdamBien
Last active June 17, 2017 01:18
Show Gist options
  • Save AdamBien/a048fa8262ad12069e94 to your computer and use it in GitHub Desktop.
Save AdamBien/a048fa8262ad12069e94 to your computer and use it in GitHub Desktop.
10thAirhacksQ&A
@realityforge
Copy link

Hi,

I noticed in this airhack you recommended against GWT due to round trip time. I wonder if this impression is based on GWT 2.7+ or earlier versions? We currently use GWT SuperDevMode + IntelliJ IDEA to develop our client side apps and even the largest has no more than 2-3 second reloads. FWIW GWT 2.7 added incremental compiles such that reloads are proportional to the size of the source code change.

When we were using GWT 2.6.1 and earlier we did find the turn-around time high and actually started to build more of our applications using JSF if they could be shoe-horned to use JSF's strengths. But after GWT 2.7 came out we actually found GWT development was faster and have gone to back to it with few regrets. I see the difference between GWT 2.6.1 and GWT 2.7 as comparable to between J2EE and EE 5. The next version of GWT (due to release in the next week or so?) that uses all the Java 8 goodness is even better.

GWT development is still complex but a significant part of that is inherent in developing SPA/browser based applications. Some of the libraries are also sucky but you get that with any toolkit that has been around 8 years or so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment