Has anybody got a chance?

["Wang, Song B" <So...@financial.wellsfargo.com>]

Hello all,

Has anybody got a chance to compare Velocity with traditional JSP? In terms
of performance? Any tradeoff out there? Thanks a lot for your input. Thx.

Song Wang
Web Developer
Wells Fargo Financial Information Services
Phone: (416) 382-5300 ext. 3367
Email: SongWang@financial.wellsfargo.com
This message may contain confidential and/or privileged information.  If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein.  If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message.
Thank you for your cooperation.


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org

Re: Has anybody got a chance?

[Barbara Baughman <ba...@utdallas.edu>]

I would add that it is infinitely easier to maintain.  Even as a
programmer who does both the programming and design on some
applications, it is easier to find and fix the applicable code when it
isn't hidden in a lot of templates.  If it's just a fix to the
presentation, I can change the template without worrying about messing
up base programming code.  As someone who has maintained both kinds of
applications, it's no contest.  Velocity wins.

Barbara Baughman
X2157

On Thu, 26 May 2005, Jason Pettiss wrote:

> The real advantages Velocity has are:
> - firmer separation of logic from presentation
> - template language that UI designers and web authors can use safely and
> learn quickly
> - no time consuming compilation step
> - macros!
> - usable scoping on included content (this is a huge advantage on a
> full-featured webapp)
>
> Traditional JSP with or without taglibs are a pretty raw deal.  They
> don't perform particularly well, implementing caching is a heroic feat,
> they crap up the internalized string pool, and they're hard to write and
> easy to break.  Taglibs really don't solve much, and can't be maintained
> by non-developers anyway.
>
> I converted a fairly busy internally used webapp, has maybe 20-30
> concurrent users on a teeny machine.  I haven't even turned off
> development mode yet and there really hasn't been any noticeable change
> in performance.  It's a LOT easier to maintain now and since the UI guys
> can just dive right in their and get dirty, it's starting to look
> *fantastic*.  A huge improvement over the HTML 1.0 widgets "look and
> feel" I had going, chuckle...
>
> Sorry no hard numbers, but, there are other advantages than raw speed
> which usually matter more.
>
> Jason Pettiss
> jason.pettiss@CatalisHealth.com
>
> Wang, Song B wrote:
>
> >Hello all,
> >
> >Has anybody got a chance to compare Velocity with traditional JSP? In terms
> >of performance? Any tradeoff out there? Thanks a lot for your input. Thx.
> >
> >Song Wang
> >Web Developer
> >Wells Fargo Financial Information Services
> >Phone: (416) 382-5300 ext. 3367
> >Email: SongWang@financial.wellsfargo.com
> >This message may contain confidential and/or privileged information.  If you
> >are not the addressee or authorized to receive this for the addressee, you
> >must not use, copy, disclose, or take any action based on this message or
> >any information herein.  If you have received this message in error, please
> >advise the sender immediately by reply e-mail and delete this message.
> >Thank you for your cooperation.
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: velocity-user-help@jakarta.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org

Re: Has anybody got a chance?

[Jason Pettiss <ja...@CatalisHealth.com>]

The real advantages Velocity has are:
- firmer separation of logic from presentation
- template language that UI designers and web authors can use safely and 
learn quickly
- no time consuming compilation step
- macros!
- usable scoping on included content (this is a huge advantage on a 
full-featured webapp)

Traditional JSP with or without taglibs are a pretty raw deal.  They 
don't perform particularly well, implementing caching is a heroic feat, 
they crap up the internalized string pool, and they're hard to write and 
easy to break.  Taglibs really don't solve much, and can't be maintained 
by non-developers anyway.

I converted a fairly busy internally used webapp, has maybe 20-30 
concurrent users on a teeny machine.  I haven't even turned off 
development mode yet and there really hasn't been any noticeable change 
in performance.  It's a LOT easier to maintain now and since the UI guys 
can just dive right in their and get dirty, it's starting to look 
*fantastic*.  A huge improvement over the HTML 1.0 widgets "look and 
feel" I had going, chuckle...

Sorry no hard numbers, but, there are other advantages than raw speed 
which usually matter more.

Jason Pettiss
jason.pettiss@CatalisHealth.com

Wang, Song B wrote:

>Hello all,
>
>Has anybody got a chance to compare Velocity with traditional JSP? In terms
>of performance? Any tradeoff out there? Thanks a lot for your input. Thx.
>
>Song Wang
>Web Developer
>Wells Fargo Financial Information Services
>Phone: (416) 382-5300 ext. 3367
>Email: SongWang@financial.wellsfargo.com
>This message may contain confidential and/or privileged information.  If you
>are not the addressee or authorized to receive this for the addressee, you
>must not use, copy, disclose, or take any action based on this message or
>any information herein.  If you have received this message in error, please
>advise the sender immediately by reply e-mail and delete this message.
>Thank you for your cooperation.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: velocity-user-help@jakarta.apache.org
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-user-help@jakarta.apache.org