On Mon, 25 Jun 2007 09:57:18 +0200, Hakim Cassimally wrote:
> On 23/06/07, chromatic <[EMAIL PROTECTED]> wrote:
>> On Friday 22 June 2007 11:07:35 Chas Owens wrote:
>> > Please, god, no. Or at least make two distributions: Bare Perl 6 and
>> > Perl 6. Many companies have a "Only Core Perl" policy. They refuse
>> > to install CPAN modules because "We don't trust them".
>> I think of this the same way I think of "Do not drink even if you mix with
>> beer" labels on bleach bottles.  Stupid people often remove their genes from
>> the pool.  We should not discourage stupid business practices from doing the
>> same.
> Releasing a language without a useful, easily installable library bundle
> could quite reasonably be construed as a stupid business practice.

I will just voice my support for putting best-of-breed modules for very
common tasks (CGI, DBI for sure) in the core.  It may not be elegant, but
it is practical... and Perl has weighed in on that side of the dilemma
before.  I think part of Perl 4's success was the "one stop shopping"
availability of numerous useful functions that would otherwise have
required linking in a library, e.g. dbmopen, crypt, shmget, gethostbyaddr,
math functions, etc.  I think the synergistic effect of the combination of
all these functions being so readily available helped Perl take off. 
Please continue the tradition of tending to err on the side of "practical"
over "elegant".  It may not seem rational that avoiding the need to type
"cpan Foo::Bar" makes a huge difference, but I believe it does, for
certain modules.

Peter Scott

Reply via email to