From what I can tell Velocity time is over. Velocity has been around for a long time, really before JSP tags had any sort of momentum in the market or best practices existed so it was very common to embed Java into your JSP..... But times have changed and we have learned from out mistakes and with the advent of MVC frameworks and JSP's we no longer have any need for Java in the JSP. Bye bye Velocity.
Final words. Velocity did solve a problem at the time but the problem was not with the technology but with the means of how we used it. Thank God for MVC frameworks!
I don't think Velocity's time is over, it is still useful in other contexts. I would have to agree that it's position as a web-templating solution has gone.
Posted by
Lance
on April 25, 2003 at 03:31 PM CDT
#
I'm going to assume here that the previous two posters have not ever either:
a) looked at the behind-the-scenes handling of JSP tag instances required by the JSP spec
or
b) profiled or benchmarked web app code with JSPs
because the extra overhead for the (negative?) benefits are just NOT worth it. That said, we still use JSPs at work, and they're what I'm most used to, but I want DESPERATELY to get to know Velocity more and use it instead. In Webwork2 we've decided to make our JSP tags (which use templates to generate the HTML output) use Velocity behind the scenes because the RequestDispatcher was making the JSP based tag templates an order of magnitude slower.
Hmmm,
a) Yep, I have. Ugly ain't it. I don't care, I didn't implement it.
and
b) Nope, cause I've never had cause for concern. My apps have handled maybe a couple hundred concurrent users - tops - without a problem, so I've never concerned myself with profiling or benchmarking them.
Ignorance is bliss ;-)
Posted by
Lance
on April 26, 2003 at 06:05 PM CDT
#
Final words. Velocity did solve a problem at the time but the problem was not with the technology but with the means of how we used it. Thank God for MVC frameworks!
Kris Thompson
Posted by Kris Thompson on April 25, 2003 at 02:59 PM CDT
Website: http://www.framework-boulder.org #
Posted by Lance on April 25, 2003 at 03:31 PM CDT #
a) looked at the behind-the-scenes handling of JSP tag instances required by the JSP spec
or
b) profiled or benchmarked web app code with JSPs
because the extra overhead for the (negative?) benefits are just NOT worth it. That said, we still use JSPs at work, and they're what I'm most used to, but I want DESPERATELY to get to know Velocity more and use it instead. In Webwork2 we've decided to make our JSP tags (which use templates to generate the HTML output) use Velocity behind the scenes because the RequestDispatcher was making the JSP based tag templates an order of magnitude slower.
Posted by Jason Carreira on April 26, 2003 at 01:17 PM CDT
Website: http://freeroller.net/page/jcarreira #
a) Yep, I have. Ugly ain't it. I don't care, I didn't implement it.
and
b) Nope, cause I've never had cause for concern. My apps have handled maybe a couple hundred concurrent users - tops - without a problem, so I've never concerned myself with profiling or benchmarking them.
Ignorance is bliss ;-)
Posted by Lance on April 26, 2003 at 06:05 PM CDT #