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 also believe that we are approaching the moment where it would be possible to do JVM dev mode without a plugin in the browser. My experiment at https://github.com/Legioth/devmodejs shows that there are only two essential features missing from Firefox: Weak references (http://wiki.ecmascript.org/doku.php?id=strawman:weak_references) to enable garbage collection in the JVM and some way of doing synchronous websocket communication (or some other synchronous communication method that does not require a new HTTP request for each round trip). -- -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "Google Web Toolkit Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
