[Tapestry-developer] Re: Tapestry vs. Turbine

[Howard M. Lewis Ship]

This is good topic for discussion on the Tapestry Developer list.   I looked at Turbine when I was first "shopping" Tapestry around for a home in Spring 2001.  The Jakarta folks didn't know me from Adam and I got the thumbs down.   I keep seeing frameworks, including WebWork and Turbine, where the framework does "everything" for you, except that you still have to write too much code to accomplish simple dispatch things.  This may be less so about Turbine now, since its shifted to a pull model which may simplify things. ----- Original Message ----- From: Misko Hevery To: [EMAIL PROTECTED] Sent: Wednesday, September 18, 2002 9:16 PM Subject: Tapestry vs. Turbine Hi Howard,             I have been developing web applications for a while and recently fell in love with Turbine (probably because I did not know about Tapestry). I think the whole JSP seriously lacks what is needed to build a web application. After studding Tapestry, I am thinking that it is one up on Turbine in terms of ease of use and development, for one your documentation is much better. The questions Is: In your opinion how much effort would it take to port a Turbine/Velocity application to Tapestry? Do you know of anyone who has done such a thing in the past?   -- Misko