Linked by Shlomi Fish on Sat 16th Oct 2004 07:28 UTC
General Development The purpose of this essay is to explain why I believe Perl 6, the way it currently seems to progress, is the wrong thing at the wrong time, and why I predict (with all the expected caveats of predicting something) that it won't be successful. I will also suggest a better alternative for the future of Perl which makes more sense at this point.
Permalink for comment
To read all comments associated with this story, please click here.
For the author: known your enemy
by Chris on Sun 17th Oct 2004 00:15 UTC

I quite thoroughly disagree with your assertion that Perl6 is the wrong way for the Perl community to be heading, but, if you're going to make that argument, you need to be able to demonstrate that you've done your research.

You complain about the lack of the . operator being available for string concatenation, and the fact that _ has been designated for that purpose. This was debated quite a bit in the mailing list, and the conclusion was that the ~ operator, which already has some connection to strings in the minds of Perl programmers (via =~), would be used instead. The _ operator was particulary onerous because _ is a valid character in an identifier. Does "foo_bar" mean the variable "foo_bar" or is it really "foo _ bar"? That ambiguity, and the fact that it would necessitate mandatory spacing killed it.

Secondly, you provide a comparison of a bit of Perl6 code with Perl5 code. Yet you're Perl6 code is better Perl6 code than your Perl5 code is Perl5 code. If you want to make a point about Perl5 being better than Perl6, you should write good Perl5 code, or people are less likely to take you seriously.

In the Perl5 code you never declare $is_ok using "my". Instead you simply assign to it. If you "use strict", as you should, your program won't run.