&gt; When I think deeply about it though, I&#x27;m not sure that any of it is better than what I experienced on a pretty big GWT project back in 2010. Yes, everyone was horrified that I was compiling Java to JavaScript. But everything just worked.<p>I used GWT in 2008 - 2010 and I would 1000% agree with you.<p>I&#x27;m currently working in a large team (100 ish Devs) for a large project written in 95% JS so I have something legit to compare with my previous experience.<p>GWT goes like this: Maven + MVP + EventBus + minimum DI + JUnit trumps the fiasco I&#x27;m dealing with JavaScript ecosystems nowadays.<p>It&#x27;s sad that GWT didn&#x27;t win mindshare due to a few reasons:<p>- Bad Rap: Java in 2006-2010 was getting a lot of heat from Rais, Google Wave was a flop (it was the most-talked GWT project)<p>- Back-end Dev rarely wants to touch Front-End development and Java developers are largely Back-end Dev<p>- Front-end Dev hates &quot;enterprisey&quot; so they refused Java and its ecosystems<p>- In general, front-end community didn&#x27;t have a solid grasp of good software practices hence perhaps they don&#x27;t quite understand the benefits of GWT (feels like I&#x27;m throwing blanketed statement but bear with me).<p>GWT was ahead (and probably still!) of everything:<p>- Dealing with Sprites and Resources a LOT easier than anything in front-end stuff we have to deal these days<p>- i18n framework built-in (have you ever seen a JS solution for i18n? doubtful)<p>- Pruning dead code!<p>- Static Analysis via Java<p>- Good Solid unit-testing framework again via Java (no QUnit vs Jasmine vs Mocha)<p>- That debugger .... very sexy!<p>- SASS? LESS? Nah... GWT has a good solution for that...(ClientBundle)<p>- Sane and Stable Date and Number formatter<p>Hm.... I&#x27;m re-thinking of using GWT again for my side project....