Friday, April 20, 2012

Compare Apache Wicket vs Vaadin

Here is the stackoverflow blog that I found which compare wicket and Vaadin.

If you are not interested in reading the whole forum then understand that Wicket has more advantages than Vaadin. Vaadin has advantages of beautiful themes but wicket can integrate with GWT.

Vaadin is better if  you just want to stick with java and not interested in CSS or javascript. But if you put in your resume that you are a web developer but not good at CSS or JavaScript then it automatically turns against you. So Vaadin wont be advantageous here. While using Wicket comes with some skills required to imagine the GUI. For developers designing GUI is also useful virtue. Does not need to be flashy but certainly useful GUI rocks.

If desktop look and feel is needed then Vaadin is good as I already suggested, but wicket is no less. You can use GWT to create such look and feels.



1 comment:

  1. Well actually Vaadin is using GWT out of the box and the Vaadin people are on googles GWT developer board. And you can easily mix it with javascript and html with it bt dont have to.
    Using vaadins customlayout you even have a very similar development style option to wicket.
    The difference is, you dont have to use these options to get productive in no time.
    That said, wicket would be my second best choice, its also a great tool but not nearly as complete as vaadin, IMO.

    ReplyDelete