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:
Abigail
Date:
July 30, 2014 15:47
Subject:
Re: Criteria for becoming/dropping a core module [was: Re:maintainer wanted: Time::Piece]
Message ID:
20140730154653.GB17802@almanda.fritz.box
On Wed, Jul 30, 2014 at 11:42:03AM -0400, Jarkko Hietaniemi wrote:
> On Wednesday-201407-30, 11:28, demerphq 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".
>
> 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.  Does  
> anyone still remember how SOAP was supposed to be the best thing since  
> sliced bread?  There was talk of including SOAP into the core.  (And to  
> be fair and balanced, also including XML-RPC.)  Group of developers,  
> let's call them X, will want all XML utils.  But group Y absolutely  
> needs CSV support, while group Z can't live without a distributed robust  
> high-performance message bus solution.  No matter how wide we stretch  
> the "more", it will not be enough.  Until it's CPAN.


Over the past decades, people have talked about releasing "toolkits".
Core + XML utils for X, Core + CSV for Y, Core + high-performance
message bus solution for Z, etc.

But I don't recall anyone actually releasing such a toolkit. (Unless
you count what's being delivered by OS vendors toolkits).



Abigail

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