Hi, Did everyone see the brief mention of Velocity in Java Developer Journal last month (June 2003)? It's an interesting editorial, complaining, in part about how many choices there are for web presentation, persistence, and frameworks. He also discusses when to innovate. To grossly over-summarize, he suggests innovating to fill a need, not to come up with a lateral technology that doesn't radically improve things. But then he makes an exception for Velocity.
...Consider Velocity, which I don't use-- it's a templating mechanism that I should use, because it fills some needs I have in fantastic ways. It's lateral, but the way it renders is very nice. It gets my personal seal of approval. "Too Much Innovation" editorial by Joseph Ettinger http://www.sys-con.com/java/article.cfm?id=2044 Best, WILL _______________________________________ Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
