JSP is like M$ technology.. its great for small projects where you really don't care if your HTML guy is actually developing a Java application in his JSP page. On the other hand, when you have a large project, having such flexible technologies is actually more of a burden than a benefit. Having a small set of well defined tools with particular purposes usually works much better. It also helps when your tools force you to do good design. This is the same issue between using VB and Java for front end development. VB can actually give you a small application faster and it will work better (at least on a Windoze platform), but I find that large VB applications are virtually unmaintainable because the tool is so flexible that it allows you to do things that you really shouldn't (such as packing your event handlers with lots of application level code similar to JSP). In terms of rating, I don't really give much force to having really tight integration with tools like that. Such tools inevitably produce code which is far from optimal. I find, rather that a small set of tools in the hands of developers who are well versed in good design principals and who are led by a developer with real vision will win out every time. Just a thought... Christian -----Original Message----- From: Jon Stevens [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 10:48 PM To: JetSpeed Subject: Re: Connection Pooling in Turbine -> J2EE on 2/5/01 9:48 PM, "Johnny Cass" <[EMAIL PROTECTED]> wrote: > I've read a lot of opinions like this one all over the net (that JSP > sucks). Though my intuition tells me that using Velocity *must* somehow > be better than using JSP, I haven't actually been able to determine > *why* this is the case. > > I have only been using JSP for about two weeks (so I may just be naive) > but have so far enjoyed it's: > > - Ease of use (but not debugging) Right, it is so easy to just put a few lines of Java code in your page, isn't it? Right there you just broke the MVC separation that everyone is so into. > - The thorough specification and documentation Yes, that part is good. However, when you have a large corporation backing the development with millions of $, you would expect such a thing. > - Level of integration (with tools like NetBeans IDE) Yes, that part is good. However, when you have a large corporation backing the development with millions of $, you would expect such a thing. Again, I'm working on my essay...it should be ready in a few days. -jon -- If you come from a Perl or PHP background, JSP is a way to take your pain to new levels. --Anonymous <http://jakarta.apache.org/velocity/> | <http://java.apache.org/turbine/> -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/[email protected]/> List Help?: [EMAIL PROTECTED] -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Search: <http://www.mail-archive.com/[email protected]/> List Help?: [EMAIL PROTECTED]
