He is saying that Perl's freedom is in a very real sense working against the goal of CPAN, and the goal of code reuse in general.

I disagree with your title, your interpretation of Anno's post, and I wonder what you think the goal of CPAN is.

If you want to embrace OO perl with enforced this or that and coding standards and whatever "professional" subset of perl you decide on - and the elitism inherent in these ideas - so be it. It's your choice.

However, perl is used by tens of thousands or people who couldn't care less what accessor methods you or Anno use, or who don't even write OO perl. And you know what? They've just as much a right to use perl and CPAN as you do, and they determine whether code passes muster the same way you do: they use it. As far as a hypothetical programmer or manager choosing X over perl ... I don't see that happening. Maybe you do, but I don't think it's appropriate to blame perl for being flexible. I'd blame the programmer or manager for being short-sighted.