All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

If you find no use from this module, I don't mind. I didn't write it for people who know precise cantrips and incantations to make Perl help them instead of allowing them to get themselves into trouble. I wrote it for people who are just learning Perl and haven't figured out yet all of the magic gobbledygook incantations to let Perl help them.

You know what you're doing. I'm trying to give the other six and a half billion people a better chance.

Please don't quote me out of context. It's rude, and it leads you into strawman arguments which waste everyone's time.

Do you remember being a novice programmer? Have you seen how they get treated in forums such as PerlMonks? If they haven't included use strict; use warnings; in their code, someone will invariable respond "I don't know how to solve your problem, but you should always use strict; use warnings;."

Given that what you wrote appears directly above my reply, I'm not sure how I'm "quoting you out of context." You're welcome to explain.

We're in violent agreement about the standard Perlmonks treatment -- chanting "use strict use warnings" at people in replies and sample code is unhelpful, and I've tried to make that point there in the past. Few novice programmers understand what strict and warnings do, but part of the process of becoming a non-novice is understanding these things. Simply adding boilerpl

Copied and pasted code that a novice has no mental framework to understand and will not understand without also understanding several fundamental concepts is magic gobbledygook. You can say "Just copy this around and don't change it and don't worry that you don't understand it," or try to explain it or make it unnecessary. I prefer the latter option.

I don't think Perl should become "Perl for dummies."

What part of Modern::Perl makes Perl more suitable for dummies? All of the

I agree, which is why Modern::Perl's syntactic disguise of the former seems counterproductive. And if believing this makes me an "arrogant, pseudo-macho jerk" and/or a "Real Man," can I at least get a card or something?

I agree, which is why Modern::Perl's syntactic disguise of the former seems counterproductive.

I wish it weren't necessary, but that requires either fixing p5p culture such that backwards-incompatible language improvements are possible or forking and promoting my own version of Perl 5. I'm not the person for either task.

At best, I can minimize the damage in a way that works right now with Perl 5.10 which is already out. There's no forking. There are no patches. No one has to recompile Perl. There are no non-core dependencies at the moment, and anyone who really can't install CPAN modules can reproduce the module in its entirety in ten lines of code.

Modern::Perl is the simplest, least bad improvement I can imagine for the problem I'm trying to address. Once novices have it installed, I can say "Here's one line you should add to all of your programs for now. It tells Perl to help find errors in your programs and makes sure that you can use all of the nice features I'm going to explain. You don't have to understand how it works for now."

I wish it weren't necessary, but that requires either fixing p5p culture such that backwards-incompatible language improvements are possible or forking and promoting my own version of Perl 5.

To be honest, that would read "changing" and "changes," not "fixing" and "improvements." You want Perl to be one thing, while the P5P regulars want it to be something else. And the module would be "Chromatic's::Perl" (apologies twice over...;-), not "Modern::Perl."