Personally, I think a lot of the bad Perl code people have had to deal with relate back to three things.
a) Many of people writing the code were sysadmins that just needed to get a job done, and didn't have much real development experience.
b) Perl was also easy to get access to in cheap shared hosting environments, so it attracted other people without some development discipline.
c) Perl4 did not have objects, and scoping was limited to local(). Thus, lots of spaghetti code and global vars.
However, none of that would have gotten exposed to developers if their teams had decent interviewing techniques, or code review, etc.
All that to say that Perl 6 shouldn't have the same propensity for bad code to end up in a real project. Any more than any other language that is. I can certainly misuse regexps, lambas and other features and write some hard to maintain Python.
a) Many of people writing the code were sysadmins that just needed to get a job done, and didn't have much real development experience.
b) Perl was also easy to get access to in cheap shared hosting environments, so it attracted other people without some development discipline.
c) Perl4 did not have objects, and scoping was limited to local(). Thus, lots of spaghetti code and global vars.
However, none of that would have gotten exposed to developers if their teams had decent interviewing techniques, or code review, etc.
All that to say that Perl 6 shouldn't have the same propensity for bad code to end up in a real project. Any more than any other language that is. I can certainly misuse regexps, lambas and other features and write some hard to maintain Python.