I think you actually have to narrow your criteria. Within jakarta commons
we try to focus on one component approach versus multiple component
approach, even though that doesn't always happen. And, in many ways,
jakarta commons has been VERY sucessful in providing reusable components.
Just look
This may not the time (or the place), but I am going to ask anyway.
It would seem that at the moment, all around the world, people are
doing the same work over and over. Particularly in regard to certain
packages/functions, this to me seems a little (well a lot) redundant.
Specifically, there
.
And I don't think it's bad. ;) And with that, a good weekend to all ;)
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Corey Scott [mailto:[EMAIL PROTECTED]
Sent: Friday, November 05, 2004 1:21 PM
To: Jakarta Commons Developers List
Subject: [OT] Aren't we all fighting
On Sat, 6 Nov 2004 02:21:09 +0800, Corey Scott [EMAIL PROTECTED] wrote:
This may not the time (or the place), but I am going to ask anyway.
It would seem that at the moment, all around the world, people are
doing the same work over and over. Particularly in regard to certain
I agree with Yoav. Diversity is good - if everyone got on one project,
everyone would have different ideas, and the tension would either tear
them apart or nothing would ever get done while they tried to agree.
Oh, and Jetspeed, Slide and Pluto probably all make components of a CMS
too (as
Thanks Martin, I hadnt seem Lenya before.
Thanks to everyone else who commented. I didnt want to sound
anti-diversity. I agree with you all diversity is good. I was trying
to suggest developing something based on standards so that integration
would be it usual nightmare.
Obviously CMS was a
