Matt was groping somewhat for cons for Wicket. This likely stemmed from
insufficient time playing with it. Every framework has its downsides,
perhaps Wicket's aren't quite so apparent.
The presentation I saw at ApacheCon was, to my mind, quite balanced. I
particularly appreciated the distinction he drew between web developer
and java developer - a web developer is very much used to the
request/response cycle, and therefore will be much better suited to a
framework that suits that. The implication is that PHP->struts is easier
than PHP->wicket. Java developers, who understand and get OO, will be
much better suited to Wicket.
The thing is, Wicket won't suit everyone, and to my mind, it is very
useful for a community such as Wicket to work out where in the web
framework landscape it sits, rather than attempting to be everything to
everyone, which it simply cannot achieve.
Regards, Upayavira
Evan Chooly wrote:
Well, then I'm glad to know that I didn't travel to amsterdam only to learn
what I already knew: Wicket is perfect!
On 7/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
Most of us already seen this presentation in Apache Con amsterdam this
year.
We came to the conclusion that all the cons he said where wicket cons
where
in our eyes pro's
so wicket didn't have any cons...
johan
On 7/30/07, Sean Sullivan <[EMAIL PROTECTED]> wrote:
fyi
Matt Raible gave a presentation at OSCON last week. The topic was
"Comparing Java Web Frameworks".
Wicket is one of the frameworks in the comparison. Matt's slides are
online
at:
http://raibledesigns.com/rd/entry/oscon_2007_comparing_java_web
Sean
