Hi Thomas,

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.

By non-mature, I mean a SDM that lacks features DM had, such as Java-level 
inspection (inspecting Java values of Java variables). I am amazed that 
nobody complains about this loss. Even if you achieve proper support for 
debugging in SDM from the IDE, will it allow such Java-level inspection ? I 
doubt it, you'll only allow JS-level inpections, while allowing Java-level 
stepping, which does not fit the GWT promise of keeping at the Java level. 
This is the reason why most of GWT developpers use it.


Le mercredi 5 mars 2014 10:15:55 UTC+1, Thomas Broyer a écrit :
>
>
>
> On Wednesday, March 5, 2014 9:30:54 AM UTC+1, Ed wrote:
>>
>> > They have to change, they have to update their tools and move forward, 
>> or quit doing Web dev.
>> Agree, that's why I spend a lot of grey hairs in using SDM, but it's 
>> simple not there yet saidly... Don't get me wrong, I wish it would as I 
>> certainly see the advantages.
>>
>
> And don't get me wrong: I'm not saying SDM is either perfect nor 100% 
> usable yet. I was just reacting to the fact people complain that DevMode 
> won't be maintained anymore as they don't *want* to move to SDM (which is 
> entirely different from your “I tried, it didn't work” situation).
> We're currently in a transition period where DevMode is already half-dead 
> and SDM isn't 100% usable yet. Hopefully SDM should be much better by the 
> next release, with incremental compilation (that'll have an impact on your 
> code to really take advantage of it).
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to