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

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

Thread Previous | Thread Next
From:
Ricardo Signes
Date:
July 30, 2014 16:21
Subject:
Re: Criteria for becoming/dropping a core module [was: Re:maintainer wanted: Time::Piece]
Message ID:
20140730162138.GA26568@cancer.codesimply.com
* Jarkko Hietaniemi <jhi@iki.fi> [2014-07-30T11:42:03]
> The problem with "more is better" approach is that the answer to "what is
> more" depends on the developers you ask, and the current fad.

This also brings to mind a quote I often think about: "The [Python] standard
library is where modules go to die."  It's not the whole view of even the
Python stdlib, but it's worth thinking about.

It's quoted at
http://www.leancrew.com/all-this/2012/04/where-modules-go-to-die/ (couldn't
find a primary link) and there's a good follow up:

> The problem with the “batteries included” philosophy of Python is that a lot
> of batteries got written back in the Python 2.0 days and haven’t been updated
> since, but because they already exist, no third party libraries catch on to
> serve the same niche.

It's Complicated.

-- 
rjbs

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