Since I am finally getting to do a Wicket project (more then a year after I first learned about it), I subscribed again to the Wicket user mailing list. Initiated by an e-mail from Erik Brakkee, I started a thread to find out how to convince Big Slow Companies (BSC) to use Wicket and finally leave Struts in peaceful history.
There was only one criterion for the items in the list: they must be one-liners that are irrefutable so that there is no place for any FUD.
Together we came to the following points:
- Wicket enables scalable development. It is easy to split the work over many developers, it is even easy to split the work for HTML people and Java people.
- Wicket provides a natural programming paradigm familiar to Java and other OO developers. There is no need to learn new languages, Java and HTML are sufficient.
- The Wicket user e-mail list provides excellent support.
- Wicket has excellent feedback messages in case something goes wrong. Furthermore, Wicket is robust and shows no weird or unexpected behavior.
- Wicket provides excellent clustering support. When required, it is possible to optimize session usage.
Although there was some strong support for including reusability and maintainability I did not do so. I have yet to find BSCs that deeply care about these issues.
Thanks go to Eelco Hillenius for his infinite ability to promote Wicket. Thanks to Che Schneider for coming up with the TLA BSC.