3 ms·
I came here to see if anyone had anything to say about this. Hadn't heard rumblings about sunsetting GWT, but the conspiracy portion of my brain wondered if Go
by techdmn 15y ago
I came here to see if anyone had anything to say about this. Hadn't heard rumblings about sunsetting GWT, but the conspiracy portion of my brain wondered if Google not trying too hard to keep the plugin up to date was a subtle push for GWT dev's to move to Chrome. :)
Last I checked the plugin for FF6 can be found here:
http://www.google.com/url?sa=D&q=https://dl.google.com/dl/gwt/plugins/firefox/1.0.10582/gwt-dev-plugin.xpi&usg=AFQjCNE1fEGhqK6BxLJNcYAlYMlPYN6Jhg http://www.google.com/url?sa=D&q=https://dl.google.com/d...
More discussion here:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/48d34a9fb54af7e6/bfc299c964a61172 http://groups.google.com/group/google-web-toolkit/browse_thr...
- allertonm 15y agoWell, the main evidence for me can be found in the leaked "Dart/Dash" memo, where GWT is referenced a few times: "The JSPrime effort was begun to unify and be a (single!) successor to GWT and Closure/JSCompiler" "What is the future of the JSCompiler and GWT? JSCompiler and GWT were already on a merger path. This effort gives us a direction for that unification around the Dash language. We will actively support teams for a long time on the current generation of JSCompiler and GWT and provide fantastic co-existence and migration tools to Dash." See: http://markmail.org/message/uro3jtoitlmq6x7t http://markmail.org/message/uro3jtoitlmq6x7t (My emphasis added. I read that as "maintenance mode".) (Edit: thanks for the heads-up on the FF6 version of the plugin - but I guess I have now missed the two-week window where both FF6 and the compatible version of the plugin where available to download!)
- DenisM 15y agoWhoa! I had no idea, thanks for sharing. This needs its own submission, so that more people can see it.