Freddy,
Thanks for the reply and as you have used Velocity so much I would love
to hear:
--> At least 3 "specific" "key" reasons why "their choice" of
templating engine was selected over JSPs and built-in TLDs?
I don't just want to hear "I use templating engine X which is great
for me" OR "because its better" OR the "best templating engine is X"... .
I honestly want to hear real CONCRETE issues that "JSPs and built-in
TLDs could not adequately solve" OR "where better solved by templating
engine X" and "moreover" WHY - in the context of large software
project development (and as far as large is concerned consider
multi-server multi-instance LB'ed 3/4-Tier deployment)?
Thanks,
--Nikolaos
Freddy Daoud wrote:
Will Hartung writes well:
I picked up Velocity, and mind I've been using it off and on since
inception which was, like, 2001. The group I was working with had
their own scheme all worked out and I beat them over the head to
convince them that Velocity was a better choice than rolling our
own.
+1 for Velocity. I've used it a lot over the years and more recently I
beat the crap out of it, using and abusing it for purposes that were
never in its job description, and it responded like a champ without
complaining.
The most recent release is May 2010 so fear not about it being
actively maintained.
Cheers,
Freddy
------------------------------------------------------------------------------
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
_______________________________________________
Stripes-users mailing list
Stripes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stripes-users
