Originally posted by Howard Lewis Ship:
Results Not Standards is the phrase Rod Johnson (the lead Spring guy) and I came up with. People are getting excellent results with Spring, Tapestry, Hibernate and a number of other non-standards. You can either follow standards, and be at the mercy of vendors, or you can choose to succeed.
Originally posted by Darrin Smith:
How about results with standards? I really don't think that following standards means that you won't succeed, but your point is well taken in that you should use what works.
My point was that if JSF and Tapestry both work, why would you use Tapestry over JSF that integrates with Spring and has the support of Sun? Unless you think that Sun is going under, and even if so, that doesn't mean that JSF wouldn't be picked up any more than it means that Java would die.
Perhaps I should have asked how well Tapestry has been received (as in how many commerical projects are using it). FWIW, I just went to Monster and searched on job openings for Java Struts (a ton came back), Java Spring (many came back), Java JSF (several came back), Java Tapestry (none came back that dealt with the Tapestry framework ).
Again, Tapestry seems nice, but I want to make sure it seems viable long term before spending too much time on it when other tools, IMHO, seem just as nice and MAY be more viable long term.
Originally posted by Junilu Lacar:
......It would be even nicer if the framework somehow forced (albeit gently) you to develop in a way that is consistent with good programming practices and conducive to good designs. Or am I asking too much?
Originally posted by Geoff Longman:
...That driver is, to paraphase Howard, "The simplest choice is the easiest choice".
Knowing that when you come up against a business problem, the easiest choice in Tapestry is the right one is a lot better than being forced. Even if its gently!
[ May 27, 2004: Message edited by: Geoff Longman ]