Peter Thomas did a great side by side you should checkout:
http://ptrthomas.wordpress.com/2008/09/04/wicket-and-gwt-compared-with-code/
Craig.
On 8-Apr-09, at 8:11 AM, Casper Bang wrote:
I was just wondering about the Wicket community's opinion of GWT. It
seems
to share many of the positive characteristics as Wicket (focus on
code, not
markup) with the major difference/benefit as I see, that is does not
maintain any state on the server. Also, with GWT you seem to get more
readily available components (i.e. http://extjs.com/explorer/). The
bennefit
of Wicket as I can see, is that applications potentially degrade
nicer and
the programming model hides the Ajax RPC better. Any thoughts?
/Casper
