There are many online decompilers. The big problem I see is that in most cases I don't *want *my code decompiled. The entire purpose of this instead of HTML5 is so that my code cannot be reproduced unless I open source it.
Also, if someone really wants a bytecode to js compiler, they can make one. I for one think that GWT is extremely helpful as is. On Monday, May 19, 2008 at 6:59:23 AM UTC-4, Axel Kittenberger wrote: > I don't think defered binding would be affected by this, would it? > Since the compiler could still chose which bytecode version to take... > > I know the decompiler approach works right now. (@hint at original > poster ;-) Would be an interesting experiment how 1) "classic java > compile" with optimization turned on 2) decompile 3) GWT compile, > affects performance/size of code. Unfortunally have no time right now, > I looked a bit into java decompilers, but this is a huge mess : > ( (either non-free, or packed with GUI, or created in some OS > dependend non-java environment, etc. None of those I looked at I would > consider good, so this needs a hack on this end too, taking a > OpenSourced decompiler and turn it into something usefull..) -- You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
