develooper Front page | perl.perl5.porters | Postings from July 2014

Re: Criteria for becoming/dropping a core module [was: Re: maintainerwanted: Time::Piece]

Thread Previous | Thread Next
From:
demerphq
Date:
July 30, 2014 16:29
Subject:
Re: Criteria for becoming/dropping a core module [was: Re: maintainerwanted: Time::Piece]
Message ID:
CANgJU+W1iYri-efa41cNDNFaQMu=5M8Vc3NYy0x388ws81B3vQ@mail.gmail.com
On 30 July 2014 18:12, Rocco Caputo <rcaputo@pobox.com> wrote:

> On Jul 30, 2014, at 11:28, demerphq <demerphq@gmail.com> wrote:
>
> I personally think that we include things we shouldn't and dont include
> things we should, and that the discussion cannot be simplified to "minimal
> core is better".
>
>
> That's easy for you to say, but when the criterion is "what people want",
> either you take the intersection of everyone's sets of crucial libraries or
> the union.  The intersection approaches "minimal core" and the union
> approaches "CPAN".
>
>
If crucial libraries means "application libraries" then I agree that CPAN
is the right place.

I personally am more concerned with the every day stuff that you need to
write an application library in the first place. Scalar::Util, List::Util,
and various friends.

On the other hand, having been in an environment that says "no CPAN
modules" before I very sympathetic with a "batteries included" approach as
well.

Yves



-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About