Vaadin vs Apache Wicket

Vaadin uses GWT to compile Java code into JavaScript. This means that developers using Vaadin can write both frontend and backend code in Java.

Vaadin has a 'design mode' which allows developers to drag and drop components into a canvas and then provide the logic for every component. There are also a lot of third party tutorials and guides which help with the initial learning curve.

The book of Vaadin is a must have for every developer that uses Vaadin to make web apps. It is an excellent reference manual and all around a great tool for every Vaadin related need. You can find and download the pdf online or get it for free in almost any Vaadin sponsored conference.

The online documentation is also very good. It has some tutorials and video guides.

There is also a vibrant community which sorround Vaadin, for any problem you may have there is a big chance that someone has already asked and answered that question on StackOverflow or in the Vaadin forums. If not, it will probably be answered quickly if you ask it.

Vaadin comes with the Valo Theme, a Sass-based theme and engine that calculates styles based on configurable variables and making it easy to define a completely new theme with a few lines of SCSS.

Vaadin has what is called the Vaadin Directory which is a repository of downloadable Vaadin components which can be easily used for development. To use something from the repository, you need to download the JAR file and add it to the project.

So it is easy to create, maintain or modify a consistent corporate design across all pages.

The HTML templates contain IDs that are references in Java code. There is no code in the templates.

That way the IDE, e.g. IDEA can verify the links already in the templates and hence there are less bad links.

Nearly everything is handled in Java code.