4 ms·

I find this kind of astonishing on the part of GWT. NPAPI has been deprecated in Chrome for more than a year, and yet GWT's development mode still depends on it

I find this kind of astonishing on the part of GWT. NPAPI has been deprecated in Chrome for more than a year, and yet GWT's development mode still depends on it?

cromwellian 12y ago
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.
kyrra 12y ago
SuperDevMode[0] has been a thing for the past year or 2 (which doesn't use the NPAPI plugin). The GWT team just released GWT 2.7 which makes SuperDevMode the default development mode (they also added incremental compilation which rocks). GWT is ready for it, the problem is that most people that use GWT are doing it in "enterprise" world, where upgrading libraries is super painful. [0] http://www.gwtproject.org/articles/superdevmode.html http://www.gwtproject.org/articles/superdevmode.html

4 ms·

I find this kind of astonishing on the part of GWT. NPAPI has been deprecated in Chrome for more than a year, and yet GWT's development mode still depends on it

by teraflop 12y ago

I find this kind of astonishing on the part of GWT. NPAPI has been deprecated in Chrome for more than a year, and yet GWT's development mode still depends on it?

cromwellian 12y ago
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.
kyrra 12y ago
SuperDevMode[0] has been a thing for the past year or 2 (which doesn't use the NPAPI plugin). The GWT team just released GWT 2.7 which makes SuperDevMode the default development mode (they also added incremental compilation which rocks). GWT is ready for it, the problem is that most people that use GWT are doing it in "enterprise" world, where upgrading libraries is super painful. [0] http://www.gwtproject.org/articles/superdevmode.html http://www.gwtproject.org/articles/superdevmode.html