I'm inclined to say that only the name is wrong. However, that would be interpreted incorrectly. Perl 6 is Perl, and I agree with the argumentation that Larry gives.

I do think the long name (including version number) should not have been Perl 6. Mind you, that includes the 6. Because the "6" part is the problem, not the "Perl" part. In my opinion, it's okay to reserve a version number only if you can deliver it within a year. Maybe two years. But it has been 7 years so far, and the end is still not in sight.

Calling it Perl 6 so long before the first release creates expectations that cannot be met, causes confusion, and demotivates people to work with and on Perl 5.

On the other hand, changing the name after 7 years may be an even worse idea. I don't know. I still like the idea of calling it "Onion" during development, and rebranding it as "Perl" when a release candidate is nigh.

Perl 6 is taking too long

I think so, but no single person is to "blame" for that. The Perl 6 we have now is not what anyone had in mind after OSCON 2000 -- if there had been releases in between, it would have taken 7 more years to come to this point, and the version would have been 8.4, or indeed 16.

Perl 6 is too much like Java

It's also too much like Ruby, too much like Python, too much like PHP, too much like Tcl, too much like Perl, and too much like C. Perl 6 is so incredibly vast, that anyone can find things they don't like about it. And we like to compare those things to other languages, because the other langugae sucks by definition. But actually, Perl 6 isn't like those languages, and it doesn't suck in the same ways. I myself try to focus on the (many!) things that I *do* think were improved, and will learn to live with the few remaining annoyances.

Perl 6 isn't Perl 5

...

Perl 6 is being designed by committee

Some complain that Perl 6 is being designed by a committee, some complain that Perl 6 is being designed by only one guy. Both are true, and some people will just never be happy. :)

Perl 6 is suffering from the second-system effect

We'll see if the second system effect is a blessing or a curse.

Perl 6 is hurting Perl 5 by consuming resources

This may have been true at one point, but it currently is not. Different people work on the different projects. In fact, very few people still work on Perl 6.

Juerd # { site => 'juerd.nl', do_not_use => 'spamtrap', perl6_server => 'feather' }

In reply to Re: What's wrong with Perl 6? by Juerd
in thread What's wrong with Perl 6? by duff

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.