I think sticking to ESR releases of Firefox could be a good approach for
keeping up with the release schedules. Even though it's not 100% trivial to
set up a system where you run the release channel and ESR at the same time,
it is still quite manageable and you only need to do it once.
I do
Another downside of DevMode maintenance is all the hacks needed in the
codebase around isScript()/@GwtScriptOnly and other magic JVM stuff. There
are still lingering bugs in HostedModeClassRewriter around SingleJsoImpls
and generics. I agree that there is nothing that works as smoothly and JVM
On Mon, Apr 15, 2013 at 8:48 PM, Ray Cromwell cromwell...@google.comwrote:
Another downside of DevMode maintenance is all the hacks needed in the
codebase around isScript()/@GwtScriptOnly and other magic JVM stuff.
Many of those hacks are there for both performance and debugging (ie, where
Hm maybe our app isn't large enough (~150 KLOC and growing) but we found
DevMode to work pretty well in Firefox. Reloading the app is a matter of
seconds and if you restart FireFox from time to time you can workaround the
current memory leak. Of course maintaining DevMode plugins is annoying
On Sat, Apr 6, 2013 at 2:05 PM, Stephen Haberman stephen.haber...@gmail.com
wrote:
For me it would be totally fine to have a plugin for FF15 and then
for FF20 and the next for FF25 which would reduce your maintaining
work. Same for Chrome.
I hold off on updating FF as well, but I believe
