The GWT team saw this coming a long time ago, that's why we undertook SuperDevMode. It's not just chrome that yanked our APIs, Firefox removed NPAPI, Safari mak

The GWT team saw this coming a long time ago, that's why we undertook SuperDevMode. It's not just chrome that yanked our APIs, Firefox removed NPAPI, Safari make it incompatible with DevMode, and the rise of mobile devices which don't run plugins, pretty make DevMode useless for mobile development. Our only options are to either ship our own browser fork, like Dartium does and like we used to do with GWT < 2.0 Hosted Mode, or to make Javascript debugging work. We opted for the latter. In GWT 2.7, we can recompile million line apps in seconds, and with Source Maps, and IDE support, you can back some of the original Java debugger experience. In IntelliJ 14 in particular, it works very nicely. Folks are working on Eclipse integration of SourceMap debugging. NPAPI is a security risk and puts restrictions on other parts of the browser internals and how they're represented. We can't prevent Chrome, Firefox, and others removing this API just because of GWT. Ironically, Microsoft might end up supporting this API forever, so GWT DevMode might continue to work with IE.