Nice Summary :) As for the learning curve, I can say from firsthand experience that I had the following experiences "learning" with both of them( this could be skewed as I spent the majority of my prof career writing either weird server/hardware device software or custom native gui based apps..not as much web stuff) :
-) After studying and reading a book (yes I felt I needed one) on Struts, as well as developing a very small prototype I felt : - Stupid - Frustrated - Confused - Trapped -) After studying and prototyping a small tapestry app I felt: - Smart for having learned it so fast - Happy to have been so productive - Relieved that web development hadn't stagnated and continued down the seemingly irreversible path of insanity that was the start of all of it with JSP. It's why I stopped doing it to begin with. There, my completely unbiased and practical opinion for your comparison pleasure. On 5/1/06, Richard Clark <[EMAIL PROTECTED]> wrote:
On 4/25/06, Jonnalagadda, Sumithra <[EMAIL PROTECTED]> wrote: > We are currently evaluating different frameworks to build our e-commerce > site. I've spent the last year and a half working on a complex web application for a Fortune 100 company using Tapestry, and I believe we wouldn't have gotten as far as we had without Tapestry. I understand your concerns about Tapestry's smaller user base, and yet our team had little trouble finding Tapestry developers and they didn't cost more than other developers. You can also get good support in this forum. We found that the "learning curve" with Tapestry was more about unlearning bad habits from other frameworks; once you understand Tapestry, the code you need to write turns out to be very clean and straightforward. And if you're having trouble learning, you can often hire Howard (at reasonable rates) to come in and teach you. (He not only came in and taught our team for 3 days, he wrote a critical piece of the system for us overnight.) Even if it takes you an extra week to learn Tapestry over some other framework, you will gain more than that back in productivity. People have mentioned that you can give a Tapestry HTML file to a web designer and the designer can change it safely. Don't underestimate that -- it's far too easy to break a file in Webwork or Struts. Tapestry also has exceptional error reporting -- it usually shows you the exact problem *and* the line and character where an error happened. (If the error is in a HTML file or a "page" file, you can change it, hit reload in the browser, and keep going.) If there's a problem in the Java, you get a complete stack trace and the rest of the information you need to find it. If you care about productivity, and building code you can maintain and change easily in the future, you owe it to yourself to take a good look at Tapestry. ...Richard --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
