|There's more than one way to do things|
I think you misunderstand me.
Because if you think that tying Perl down with bondange and discipline...
If Perl::Critic were not customizable, I wouldn't use it. I wouldn't recommend it.
I think it's valuable, in the same way that I think having coding standards are valuable, but I don't think you'd adopt mine wholesale, nor should you.
I use Perl::Critic as an example of a new tool that can help people improve their code. I think Perl Best Practices is a good book which discusses how people can improve their code. I don't apply every practice when I code, and I'm sure Damian's fine with that.
I do mind if someone's rolling his own blessed hash objects with the ref $self || $self idiom and fragile subclassing problems, because there are better solutions that exist that somehow we need to evangelize through the entire Perl community, not just the insular percentages that frequent the top Perl forums in the world.
Enforcing B&D for everyone at the language level is wrong, but providing sane defaults and giving people the option to turn the thumbscrews to their desired level of pain or pleasure makes more sense. I think it's even Perlish.
I fear you are not the Saviour of P6 as I thought you might be.
Never claimed to be, nor wanted to be. (I do think roles are pretty awesome, and I'm happy to share some credit for them.) You might be pleased to learn that I did howl when the idea came up of making classes closed by default. Fortunately, no one suggested that seriously.