[EMAIL PROTECTED] (Erik Norgaard) writes:
> I just browsed through the namespace guidelines and the concern
> about avoiding the namspace to clutter up.
Namespaces had their day when there was no easy way to search CPAN, and we had
to just browse to the modules we want. Now we have a full-text search of the
module's documentation at search.cpan.org, browsing is considerably less
important, and namespaces are just a quaint idea.
Every few months, there's a discussion here about how to fix CPAN, with nobody
really establishing that CPAN actually needs to be fixed; even if a concensus
is reached, nothing ever gets done about it, and the things that do get done
are generally the result of individuals having the right amount of JFDI and
acting first and seeking forgiveness later.
That said, I encourage people to continue debating what should be done about
CPAN namespaces, because it keeps people busy. The intersection of the set of
people who have interesting ideas about how to make CPAN better and the set of
people who actually contribute a substantial volume of useful modules to CPAN
is sufficiently small that I have no qualms about them continuing to be tied
up in endless and fruitless discussion.
--
COBOL is for morons.
-- E.W. Dijkstra
