FWIW, I'd like to replace the pros and cons (my opinions) with some that are more accurate. As users of Wicket, I'd love to hear from you and get your opinions on the top 3 pros and cons of Wicket.
Here's the ones I currently have: Pros: * Great for Java developers, not web developers * Tight binding between pages and views * Active community - support from the creators Cons: * HTML templates live next to Java code * Need to have a good grasp of OO * The Wicket Way - everything done in Java IMO, there's no need to debate whether these are valid or not. If they're not - please suggest new ones. James Ward of Flex had a nice and honest comment this morning pointing out Flex's cons: http://tinyurl.com/yvybnm Thanks, Matt Sean Sullivan-3 wrote: > > fyi > > http://raibledesigns.com/rd/entry/comparing_jvm_web_frameworks_presentation > -- View this message in context: http://www.nabble.com/Matt-Raible%27s-ApacheCon-presentation-tf4815955.html#a13780071 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
