Link Details

>>> It isn't the ideal technology choice to do prototyping

 >>> making even sample application working take time and effort [code class="java"] Did you try utilizing one of the (gwt-)maven archetypes available? That should enable anyone to create a "GWT development best practices" application from scratch within a few minutes ( e.g. http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html ). 

[code class="java"][/code> >>> (using embedded Jetty), testing a small change of the source code take long time That sounds odd. Small changes in client code should always recompile pretty much instantly while in development mode. What kind of hardware are you using and how much memory do you allocate for the JVM ( -Xmx... )? >>> In the reality the generated java script is not really cross browser compatible (as promised) Could you please elaborate or give a simple example? >>> Documentation isn't the biggest advantage of GWT Agreed, again.

How does formatting work in these comments!? [[---quote---]] It isn't the ideal technology choice to do prototyping [[---comment---]] Agreed. [[---quote---]] making even sample application working take time and effort [[---comment---]] Did you try utilizing one of the (gwt-)maven archetypes available? That should enable anyone to create a "GWT development best practices" application from scratch within a few minutes ( e.g. http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html ). [[---quote---]] (using embedded Jetty), testing a small change of the source code take long time [[---comment---]] That sounds odd. Small changes in client code should always recompile pretty much instantly while in development mode. What kind of hardware are you using and how much memory do you allocate for the JVM ( -Xmx... )? [[---quote---]] In the reality the generated java script is not really cross browser compatible (as promised) [[---comment---]] Could you please elaborate or give a simple example? [[---quote---]] Documentation isn't the biggest advantage of GWT [[---comment---]] Agreed, again.

Thank you for sharing your knowledgeable with us. <<>> In the reality the generated java script is not really cross browser compatible (as promised) <<>> Could you please elaborate or give a simple example? <<>> I'll check in our bug trucking tool, I'm sure that we fixed some bugs concerning the compatibility between IE and firefox. <<>> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html >> We are already using this archetype but it's only create a sample application. But I don't agree that the generated application contains the "best practices''.Just to create 2 screens, you need to create: 2 places, 2 activities, , DTO, View, ViewImpl class, UIBinder file, some events, some event handlers, place mappers, module inject...lot of plumbing.

GWT probably isn't future-proof. I'd stick to JSF2.

i had started learning GWT , but as Goog started pulling the rugs off its feet , i gave up. now i a happy with my decision i made a year ago. :-)