Hi there,

I don't think I am getting power away from über-users when I say I prefer strict and warnings on by default for Perl 6. Nor I think I am leaning towards the newbie camp too much. Perl is a complex language with a steep learning curve at first, specially considering they are teaching Java in the schools now, which distorts their minds into a particularly narrow viewpoint of programming and designing. If everybody say strict should be used, and man perl itself considers warning off by default a Perl bug, I'd say it's simply putting explicitely what many newbies (and not so newbies, either) learn the hard way over the time.

If we free their minds from those troubles from the start they can pursue better things like mastering the rest of the language, which is a feat by itself.

We all have seen (and many written) code like this before:

use strict;
...
    for my $fun ( @funs )
    {
        no strict 'refs';
        *{__PACKAGE__::"$fun"} = sub { blah blah blah }
    }
[download]

... or similar code. We would be just getting rid of two explicit declarations that many people forget to write in their programs. Maybe the explicit telling of them is a good exercise of thoughtfulness and responsibility by itself, I wouldn't disagree to that, but we know from experience that many Perl programmers do not raise to the challenge, and this creates a distrusting fame around the language that affects negatively to all programmers, good and not.

Considering that some people do work using Perl, we don't need to keep feeding the suits with distorted views of the reliability and power of Perl to make a project; enough hype surrounds them from other camps.

I am just trying to be pragmatic and practical...

Best regards,

--
our $Perl6 is Fantastic;