<loop repeat="infinite">
<voice tone="robotic">
Do not try to resist.
We must use Turbine.
JSP is futile.
Turbine is the only solution.
We are Borg.
Only Turbine knows the way.
We will assimilate you.
</voice>
</loop>
"Choose your enemies wisely ... for you will become them."
> Needless to say, I think that I'm going to start doing my own
comparisons and placing them up for people to comment.
Choice is good. Let's have more choice.
> you are arguing that it code re-use is a bad thing and we all know
that isn't true.
Creating better products with less effort is good.
When code reuse contributes to that goal, then code reuse is a good
thing.
But code reuse is neither the goal nor a panacea.
If this is a meritocracy, and decision-making is being push down, then
a subproject is entitled, even obligated, to decide for itself when it
is better to rewrite than reuse.
Of course, anyone who disagrees can always make a proposal, provide a
working alternative, and let the subproject Committers decide what's
best for the product and its users. At least if this is really a
meritocracy.
It's also important to remember that Java is a components-based
architecture. It would be reasonable for a product to provide a simple,
easy-to-configure solution as part of the release package, and then
also document how to hook into more full-featured solutions, including
a special-purpose Jakarta product, like a datasource pool. Choice is
good.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
