Gabe, I agree that performance is an important factor (as you say, among others). But when you say that Velocity has "lost ground", do you mean relative to other templating engines? Or do you mean relative to JSP?
If you mean relative to JSP, it seems to me that the biggest advantage of Velocity (and perhaps other templating approaches too) vis-a-vis JSP has never been speed (most suggestions were that Velocity might be marginally, but not dramatically, faster), but in "ease of use". Even if, as you say, JSP engines are faster now, doesn't that still leave the more important "ease of use" issue favoring templates? Regards, Terry ----- Original Message ----- From: "Gabriel Sidler" <[EMAIL PROTECTED]> To: "Velocity Developers List" <[EMAIL PROTECTED]> Sent: Monday, March 03, 2003 8:26 AM Subject: Re: AW: velocity 1.3.1 final? > > Terry Steichen wrote: > > > I too use Velocity and find it quite stable. I've also extended it (as have > > most) with specialized tools, and as a result, it does precisely what I want > > it to do. I agree that it's important to take a look at the bug processing > > and make sure it is robust. But I don't understand your comment about > > losing ground in comparision to other engines. What does that mean in terms > > of being able to do things with other alternatives that you can't do with > > Velocity? > > > One area is speed. JSP Engines have improved a lot in terms of speed over the > last two years. For my types of applications, Resin processes JSP templates > about two to three times faster than Velocity templates. Tomcat has improved a > lot as well. One or two years ago, JSP and Velocity were comparable in terms > of speed. This is not true anymore for the types of application I run. > > Now, performance is one among many evaluation criteria for a templating > solution and rarely the most import one. Nevertheless, this is an area were > Velocity has lost ground. > > Gabe > > > > > > > Regards, > > > > Terry > > > > ----- Original Message ----- > > From: "xMySign for Velocity" <[EMAIL PROTECTED]> > > To: "Velocity Developers List" <[EMAIL PROTECTED]> > > Sent: Monday, March 03, 2003 3:46 AM > > Subject: AW: AW: velocity 1.3.1 final? > > > > > > > >>Is there something in particular which is preventing you from using > >>the stable or development branches of Velocity? > >> > > > > I'm using Velocity and it is quite stable, but it really > > lost ground in comparison with other template engines, > > and - that's the most important thing - there are quite > > a few bugs reported (have a look at the archives) and > > no one is fixing them, or - even worse - someone fixed > > it, but no one reviewed the patch so the bug is still left > > in the code. IMHO that's not the right way to find some > > interested commiters. > > I really would like to hear something about the thoughts > > of the current committers. what should be the future of > > Velocity? How we can find a lead? > > > > mike > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
