Now with GWT2, what are the advantages over wicket and likewise?
- by Antony Stubbs
Apart from the argument of wicket's simplicity (that is, wicket is a simpler system IMHO) and GWT's responsiveness in the client (GWT's client side state and javascript - potentially complex client side code) and GWT's greater potential for scaling, what is the argument for using GWT over wicket?
Personally I've done a lot of wicket development, but have only had a quick look at GWT a long time ago.