Re: Extensions User Design - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Extensions User Design
Date
Msg-id 38E2A931-8205-498C-9A57-37F3067B705A@kineticode.com
Whole thread Raw
In response to Re: Extensions User Design  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Jun 24, 2009, at 2:07 PM, Andrew Dunstan wrote:

> Actually, I think we should be like Perl here. There is a list of  
> standard modules that comes with the base Perl distro, and then  
> there are addons, such as you find on CPAN.

Actually, the lesson slowly emerging in the Perl community is that  
there should be very few extensions distributed with the core, as  
keeping them in sync is a giant PITA and in part responsible for the  
duration of time between releases.

A separate distribution of "recommended extensions" would fill the  
same need, but not bind core to the schedule of extension updates.

> Beyond standard extensions, I'm not sure we need a committee to  
> "approve" extensions. Does Perl have such an animal? I'm fairly wary  
> of creating new decision-making bureaucracies.

Agreed. Perl does not have such a thing. PHP does, and it's no doubt  
part of the reason that PEAR has so few modules.

Best,

David



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Extensions User Design
Next
From: "David E. Wheeler"
Date:
Subject: Re: Extensions User Design