> > I just realized that lack of Firefox 27+ support for dev mode recently > (tried it because Chrome's plugin crashed too often) and really think this > is a shoot in the foot for GWT : even if you don't control Mozilla choices > of course, forcing to move to a non-mature SDM is very risky for GWT itself. >
But there is no other viable solution and the transition was actually planed more smoothly. I can understand that many people can not use SDM just because the SDM compilation is too slow for their project. But I don't understand people saying that debugging with SDM is a pain. Yeah for a Java developer it is strange to leave the IDE but honestly for every day debugging browsers provide everything you need. There may be some hiccups here and there but overall it is useable and it is not at all comparable to the situation around the time GWT was invented. Back in these days "use your Java debugging tools" was a very strong argument but today browsers have catch up and will continue to catch up. If GWT will provide debugging in IDEs with SDM then it is only for convenience. You must become a web developer even if choosing GWT and you should understand the browser platform sooner or later just like you need to understand Swing when doing Java Desktop apps. I think the most risky thing of GWT proper was to ignore mobile too long and now it has to catch up quickly. With this in mind, SDM is actually a huge plus for GWT because it enables you to build/debug mobile apps more easily. With DevMode only, developing mobile apps is painful. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
