I’m not an Expert. But I have worked with web frameworks in the last two years. During those years i have tried to find easier ways to do basic user interfaces. It has always been recoding this and reusing that. What if the world of web development could start being effective?
And then Wicket comes into the picture. It doesnt make the case any better. Actually, wicket is the rant for this article.
Wicket uses abstraction and inheritance to develop interfaces. Mostly like we do with Swing. But does it really make the cut?
With developing web applications as a daily job, boilerplate is always an issue. And with wicket that boilerplate issue increases. Yes i can make reusable components, but that doesnt advocate its use as an out of the box framework. Its very difficult to make a dropdown menu per example whereas in web flow this is just a template.
To conclude: wicket cant stand up to Spring Web Flow when it comes to speed of development. I can make a flow app from Pojo in about one hour that actually works. With wicket i have to code, compile, package and test. In flow i can just edit a flow definition or two.
I Think Ill keep on using Spring for my development.
Recent Comments