The flexibility of T5, in that almost every task it performs is handled by a different service that can be overwritten has a downfall. It sometimes takes me a long time to figure out what service handles what task and how can it be overwritten (the under documentation argument obviously plays a role here). Some of the reflection can make debugging harder at times and annotations over POJO's takes some time to get used to (but maybe that is a java5+ wide argument).
My 2 cents, Joost On Thu, Apr 30, 2009 at 8:19 AM, Inge Solvoll <inge.tapes...@gmail.com> wrote: > Hi! > > I have been reading the "beautiful" thread and added my opinion about what's > great about Tapestry. It's nice to sum up why we all are so excited about > this, it obviously makes both us and the creator(s) feel good about > ourselves. But for a little while, I challenge us all to stop tapping each > others' backs and go into depth about what's not to like about our beloved > framework. > > The most obvious questions that could be asked probably have some very > obvious answers. But T5, as I see it, is all about addressing stuff that > other frameworks have given up on and create excellent implementations > rather than just looking the other way. Difficult and uncomfortable > questions should be addressed the same way. > > So: > > What are the main reasons that T5 isn't one of the "big ones", when we all > seem to agree that it is so much better than most other frameworks out > there? Why is T5 NOT beautiful? > > Hope I'm not insulting anyone, I'm a big fan too, I just think this actually > could lead to significant insight :) > > Regards > > Inge > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
