Not to open an old wound.....but Tapestry's mantra is "static components, dynamic behavior", and that seems very crippling to me from an enterprise development level. You don't have to go far in enterprise development to need dynamic components. Yes, I know, Tapestry can do dynamic components, but it's not a natural process and it is poorly--very poorly--documented.
Someone commented to me that they thought Tapestry had an infinite learning curve. I disagreed. I said, it has a steep learning curve, but then it levels off. If you stay on the narrow beaten path, you can sprint. But if you deviate, your sprint frequently encounters wall after wall (e.g., application catalogs in 3.x). In an enterprise environment, the walls appear pretty quickly. Those walls would disappear, or at least become speed bumps, if these problems were addressed: Dynamic Components Documentation / Quantity and variety of Books Advanced Examples Backwards Compatibility / Kind Migration Path Bug Fixes for 3.x Better i18n Support As a result, these larger issues arise: No confidence in reuse Few widget libraries of consequence, if any Lack of talent on the street Lengthy development cycles Questionable maintainability Tapestry does a lot of things right, but they tend to be technically "cool" things. Work days, at least in English, are called "business days" for reason. - Mike "John Coleman" <[EMAIL PROTECTED]> 03/22/2006 03:21 PM Please respond to "Tapestry users" <tapestry-user@jakarta.apache.org> To "Tapestry users" <tapestry-user@jakarta.apache.org> cc Subject Re: promoting Tapestry PS: I've been working on Blue Martini and Hibris Jakarta for the last year or so, and both are horrible. If these kind of systems were developed in Tapestry, they might actually be affordable to develop and maintain by a much wider audence. A quality eCommerce solution is still much in need, the existing JSP based ones are really too painful. The thing is, I can see the big package vendors adopting JSF eventually, but Tapestry? John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
