You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@commons.apache.org by "Daniel F. Savarese" <df...@savarese.org> on 2003/09/18 19:08:04 UTC

Re: Purpose of Multiple Commons was Re: DbUtils

In message <Pi...@umbongo.flamefew.net>, Henr
i Yandell writes:
>This is also short-sighted. There is a very strong language barrier
>between Java and other languages. It's not a wonderful thing to have, but
>pretending that it's the same strength as C to Tcl, or Perl to Python will
>just ostracise the Java [read Jakarta] bits more.

Here's my take.  Consumers of libraries just want canned code that solves
a problem they're facing.  They don't care if the code happens to reside
along with other libraries written in/for different languages.  After
categorizing by functionality, you still have to subcategorize by language
so a programmer doesn't download a C++ theorem proving library when he needs
one in Lisp (nevermind that a C or C++ library can offer multiple language
bindings--an approach I would favor for Apache Commons projects).  I don't
believe Jakarta Commons/XML Commons/etc. projects should be forced to move
into Apache Commons (if that's what we're talking about), but I believe some
of their components would be better served in Apache Commons once it gets
off the ground.  I may have lost the point of the discussion, in which case
just ignore what I said.

daniel



Re: Purpose of Multiple Commons

Posted by Greg Stein <gs...@lyra.org>.
On Thu, Sep 18, 2003 at 01:08:04PM -0400, Daniel F. Savarese wrote:
>...
> Here's my take.  Consumers of libraries just want canned code that solves
> a problem they're facing.  They don't care if the code happens to reside
> along with other libraries written in/for different languages.  After
> categorizing by functionality, you still have to subcategorize by language

Agreed.

>...
> I don't
> believe Jakarta Commons/XML Commons/etc. projects should be forced to move
> into Apache Commons

Agreed, although I would hope that (in the long run), all of the various
commons projects will become unified by choice.

> (if that's what we're talking about),

Nope. The thread is really why we might have multiple Commons projects,
and also partly to answer "which one is best for my component?"

Migration of existing components from Foo Commons into Apache Commons is a
choice of the dev community, and a vote from the two relevant PMCs (the
existing governance PMC, and the Commons PMC) to allow the move.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/