With the correct project refactorings that simplify some of the annoying
issues of Tapestry (its abuse of abstract classes, some counterintuitive
idioms like lazy initialization for properties and the event system
order - IMO) I think Tapestry could be the next Hibernate.
Unlike Hibernate (which I use since 2002 - when it was a small project
and Gavin didn't have his head full of JBoss air), Web frameworks have
intense competition, including JSF. But, I think, if this is managed
properly then it can happen all over again, a bloated standard getting
beaten by a working framework.
So, IMO, Tapestry has a great future ahead!! Again, to the committers:
please focus on cleaning up, documenting things properly, and giving an
overall "polished" feel to the framework (which it still lacks a bit).
That's easy to do and will calm the concerns of people like Lennart, I
think.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Lennart Benoot wrote:
Hi Howard and all,
Honestly speaking, this is a strange mail.
Should the tapestry community get their instructions/hints before leaving their
mailing list and venture the wide world on theserverside?
I don't think so.
Anyway, doesn't really matter. I think instead, effort should put into making tapestry more attractive. As I allready mentioned a few times, tapestry is attractive from a technology point of view.
Looking at other domains, tapestry has a long road to walk. I have the
impression that nobody isn't really putting effort into it. Given the fact that
we are feeling the hot breath of other technologies such as jsf, this starts to
bother me. I'm am investing a lot into this technology and I wouldn't want it
to become a marginal framework used by die hard fans only.
What do you guys think about it?
Regards,
Lennart
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
