> I've just spent whole January, four hours a week, teaching Tapestry in a
> large company with lots of people working in large projects, including one
> that will be used nationwide in Brazil. The standard argument doesn't
> convince me: JSF is a mess and it is a standard. It suffers from the
> every-stakeholder-must-be-pleased disease you mentioned above, and most of
> the stakeholders were tool makers, not application makers. Spring is not a
> standard, but has lots of users, including large businesses. Hibernate and
> Hibernate Validator weren't standards, but were so widely praised and used
> that helped shape JSRs.

I agree. But want to add that it is important to integrate with
standard technologies. After all tapestry needs to be able to make use
of them and integrate where neccessary.

If someone develops a Java webapp, he does not want to re-invent
everything just because of a superior component framework. There is
other stuff like persistence, transactions, remote services and so
much more that needs to be available out of the box. Without
integrating them yourself. And yes, I've brought this up one or two
times already ;)

We are getting there - with contributions from the community. But we
need to make them more visible and communicate that it is totally OK
to use them, even if it is not part of the tapestry core. Maybe we
even need to think about making them part of Tapestry in some way
(official extension library or whatever).

> Regarding the "cool" part, something that really stands out about some other
> frameworks like Vaadin (http://vaadin.com/home) and Play
> (http://www.playframework.org/) are their websites' design. They're really
> beautiful, they have a step-by-step tutorial linked in the first page, they
> have very organised documentation. All that give them a nice impression
> outright. Sometimes I think Tapestry needs a web designer more than anything
> else. :) Then I remember how bad I am at design. www.arsmachina.com.br for
> an example of that.

Totally agreed! We need a web designer. And more important: we need to
start building a community. My impression is tapestry was never good
in building a community around it.

            Piero

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to