Antwort: Re: Antwort: Wicket community traction / Wicket Web 2.0 experience

[christoph . grothaus]

Hi Bruno,

I appreciate it that you pray for the rest of my team :-) I won't be a bad 
looser, so I will give my best with the other devs to build a good 
solution with GWT. I really hope that it is not inherent to GWT that the 
code gets big and unmaintainable. So I cross my fingers and hope for the 
best...

Kind regards,
Christoph

Antwort: Wicket community traction / Wicket Web 2.0 experience

[christoph . grothaus]

Martin, Richard, thanks for your answers!

Unfortunately, I could not convince the other devs of the various 
advantages of wicket. The team chose GWT because it allows to create Web 
2.0 style user interfaces with fewer effort.

Regards,
Christoph

Wicket community traction / Wicket Web 2.0 experience

[christoph . grothaus]

Hi Wicket users!

At my company, we are currently evaluating technology choices for building 
web user interfaces. We narrowed our candidate list down to two remaining 
candidates: Wicket and GWT. We already did some prototyping with these 
two. Our main conclusions are
- Wicket has the better architecture (by far).
- GWT allows to create Web 2.0 style user interfaces with fewer effort.

I like Wicket because of the first argument. In our team, there are some 
objections against Wicket because of the second point and because some 
developers in the team think, that Wicket has not enough community 
traction and that no serious Web 2.0 _application_ uses Wicket.

Can you help me to invalidate these objections and to convince my team of 
Wicket?
- Which Wicket success stories do you know of?
- Are there examples for serious Wicket applications?
- How can I prove that there is community traction for Wicket?
- Are there examples of a GWT style Wicket usage, that means lot of Web 
2.0 user interface features realized with Wicket?

Regards,
Christoph