> Bugward compatibility takes a backseat to correctness for example.
This is the problem. The perfect (p5p) is the enemy of the good (CPAN).
How can it be acceptable that "fixing" Perl is "breaking" CPAN? I noticed
the breaking changes tend to reduce the DWIM nature of perl in favor of some
abstract notion of what is correct, like for example, my $foo qw(bar baz) makes
perfect sense and was valid perl until some programming justice warriors decided that
breaking backcompat was less important than their idea of programming correctness.
The result is broken scientific distros sitting on CPAN forever because, for example, we now have to --force install and add 2 characters to 1 module to fix 3 modules. Someone who is more of a scientist than a perl programmer will shrug their shoulders and move on to a programming language with working libraries. It's a dire situation!
Thank you Corion and daxim for your thoughtful replies and valuable information (but that anonymous reply, get an account! =)