On Fri, Nov 16, 2007 at 09:54:39AM -0800, Curtis Cooley wrote: > Michael Laccetti wrote: > > John Krasnay wrote: > >> To me this is the biggest con. I've worked with a number of Java devs > >> who have trouble grokking anonymous inner classes, which you must know > >> cold to be effective with Wicket. > > > > Quite a con indeed. Wicket is not a framework that most people new to > > Java/OO can easily jump into and start churning out apps with. This > > ties together with the concept of models, and figuring out which is > > the right for the situation. There is no easy answer, it is more of > > an instinctive "feel" that you get over time. > > > > It is inherently worse for people that were Struts devs. It took me a > > while to unlearn my view of the world. > > > You have to know OO and grok anonymous inner classes to program in Swing > and you have to know OO to program in SWT, so why wouldn't you need to > know OO to program a web framework. If you're going to be a Java > programmer, then learn OO. If you don't want to learn OO, then write > .NET and get used to maintenance hell. >
On second thought, you're right. Listing this as a Wicket con is a bit like saying "Your team may not be smart enough to use Wicket," which I don't think would go over very well at Matt's presentation. jk --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
