Well there's one person there who had negative comments. At the end of the day different people will prefer different frameworks - perhaps some aspect of a framework is more suited to particular project requirements, or maybe more generally suits a person's way of thinking or code style.
For me I started out using Wicket and then was introduced to Tapestry 5 - and have not looked back. The dev cycle is much faster and it's much less verbose. The mailing list is extremely active with plenty of very experienced users contributing daily. And yes Tapestry is powering many enterprise/serious projects. It's far from complete, but some are listed here: http://wiki.apache.org/tapestry/PoweredByTapestry And as for documentation, Howard et al have done a great job pulling together updated docs. You can find them here: http://tapestry.apache.org/ The problem I think Tapestry has had is one with PR. I think a few people got disillusioned with backwards incompatability between major versions and moved elsewhere. However I know Howard and the Committers are doing everything they can to address this. That's my 2 cents; I'm sure others will be able to give you a more compelling/detailed justification for Tapestry. Richard. On Tue, 2010-12-21 at 11:48 +0100, George Banus wrote: > Hi, > > I am a newbie to Tapestry and while googling to learn more about tapestry, I > found this discussion going on at > http://www.theserverside.com/news/thread.tss?thread_id=61537. Some of the > comments look very disappointing. > Is Tapestry really used for serious projects? > > George --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
