I remember in my previous company how emphatically someone sold Python to the management. It was just brilliant. If I have to do the same with tapestry can you tell me some nice things that i can tell the 'management'. I do understand that I first need to be convinced that tapestry is better than most frameworks. It will definitely take a while. Either way, would a slide to slide comparison with struts help given the fact that struts is all over the place these days?
I'm finding these JavaRanch forums a bit hard to navigate and monitor.
Yes, my four principles Simplicity, Consistency, Efficiency and Feedback are a very programmer-way of describing the benefits of Tapestry. In fact, I apply them to all my frameworks and tools. I think they are good notes for explaining the benefits of Tapestry to management.
More off the top of my head thoughts:
You get the same work done in Tapestry, but the end result is reached faster and the end product is more robust, since it is leveraging years of development and experience.
Why is it faster? The fastest code is the code you don't write and in Tapestry you write a lot less code. In addition, it is much easier to combine pages written by different developers, and it's natural to create reusable components for your application.
Why is it more robust? Tapestry's component object model means more checking can occur at runtime. And if you use Spindle, lots of those checks move to build time, literally, every time you save a file.
--<br />Howard M. Lewis Ship<br />Independent J2EE / Open-Source Java Consultant<br />Creator, Jakarta Tapestry<br />Creator, Jakarta HiveMind<br /><a href="http://howardlewisship.com" target="_blank" rel="nofollow">http://howardlewisship.com</a>