title: Wicket vs Vaadin
body: <p>I am torn between Wicket and Vaadin. I am starting a micro-isv and need to make a choice of web framework. I have narrowed down my choices to Wicket and Vaadin. I have used both frameworks and I love them both. however I need to make a choice. </p>
  
  <p>If If I choose Vaadin:</p>
  
  <ol>
  <li>I wont have to worry much about the look and feel. It comes with nice themes.</li>
  <li>I will do all my programming in Java which am very good at and wont have to spend time hacking CSS which am not very good at.</li>
  <li>And most of the components that I will need for a business applications are there OUT OF THE BOX including, desktop like layout, tooltips, Keyboard shortcuts, tables with draggable and collapsible columns to name a few.</li>
  </ol>
  
  <p>However, if I go the Vaadin way:</p>
  
  <ol>
  <li>I will loose the ability to create UI declaratively.</li>
  <li>I wont have the fallback feature if the browser doesn't support JavaScript - e.g most non Webkit mobile browsers.</li>
  <li>Vaadin company is selling some components - e.g the JPAContainer so am not sure the company will be committed to offering full open-source framework. Business interests will always come first.</li>
  <li>Vaadin applications will be mostly for the intranet. They are not very suitable for the internet with a web look and feel.</li>
  </ol>
  
  <p>If I go the Wicket way:</p>
  
  <ol>
  <li>I will have to style my applications and I can hardly give them a desktop look and feel. </li>
  </ol>
  
  <p>Any advice? Anyone with experience on either framework kindly tell me the cons and pros and how you made your decision. </p>