Hi All,

Tomorrow is our last day of debate at my work about which framework to
choose for our upcoming huge project.
Its seems Wicket is winning the race for it's innovativeness, finess and
excellent support, they claim, unfortunately. Most on my team members are
concerned about the radically incompatible versions Tapestry has. And many
say Tapestry 5 is over engineerd and has already lost the webframework
battle and are concerned of it's future, in terms of upgrade and support.
Could someone here offer me some killer arguments to counterfight these FUDs
of my team?

Regards,

Rob

Reply via email to