I think Kranga is spot on. As a software engineer, my personal opinion is, that from a technical point of view Tapestry 5 is the best framework out there. However, going to client sites aiming to convince the stakeholders to adopt T5 is extremely difficult because they have absolutely no technical knowledge.
Alex is right that the core of Tapestry 5 is quite stable and we can still fix Tapestry 5 bugs ourselves. However, putting such an argument in front of a Chief Technology Officer or a Chief Architect begs for the following response. "I do not have the budget, time or interest to develop another web framework. I want to use an existing one to implement my business requirements ASAP and with a minimum budget" Petros kranga wrote: > > The question is very relevant. The concern of the project should be to > build > out the business functionality using existing tools. If the tools in > question are not yet released and in production, there is a very > legitimate > concern that the maintenance of the tool will become a partial focus. > Tapestry may be a compelling offering technologically, but it has many > other > factors going against it - lack of a developer mindshare, incompatible > releases in the past, etc. We have used Tapestry for big projects - but we > are still using T3 since T4 and T5 are completely incompatible. You cannot > push beta software past project stakeholders unless that beta software is > also providing you with competitive advantage. T5 has some able > competitors > in Wicket and JSF/Stripes, etc while still lacking an ajax foundation for > instance. So the competitive advantage is not clear cut. > > ----- Original Message ----- > From: "Alex Shneyderman" <[EMAIL PROTECTED]> > To: "Tapestry users" <users@tapestry.apache.org> > Sent: Thursday, October 18, 2007 3:22 AM > Subject: Re: Tapestry 5 Roadmap > > >>> The one question I could not answer without looking ridiculous was "What >>> happens to our multi-million dollar project if Howard is hit by a bus >>> tomorrow" >> >> I think the question is irrelevant. The question you should be answering: >> Is the current base usable enough to push through on the project?. A >> relevant after-question (if answer to the above is not exactly) to answer >> how easy it is to add the features you are missing if you have to. And >> how easy it is to poke through the tapestry's source-base to fix bugs >> that >> might exist and you will find during the project's development. >> >> If you can cross off HLS as your dependency then t5 is probably the best >> choice to make from what's available out there :-) >> >> Alex. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Tapestry-5-Roadmap-tf4439437.html#a13273517 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
