No offense, but Duh!

Then I really don't understand the question.

If you know that you have to evaluate when you can use Rakudo Perl 6, why does the version number matter? There was even serious talk about not having version numbers to avoid all of the mystical magical thinking that surrounds version numbers.

For goodness's sake, cpan.org even had "Don't use Perl 5.10.0 in production; it's only for testing!" because it had that mystical, mythical, might-eat-your-data trailing ".0" in the version number.

I use a bunch of open source apps versioned at .01 or .5 or whatever the author(s) think appropriate, to indicate that it does more or less what they set out to do, but isn't done or isn't polished or has bugs or a list of to-dos or whatever. Same with Perl modules. They do what I need, so I'm not concerned with the version number.

Like I said, we're not into magical version number thinking. We could have slapped 6.0.0 on any tarball in the past couple of years and people would still have to evaluate it on their own.

Is it really so unreasonable to ask how that's coming along?

What you actually wrote was:

Asking about a Perl 6 release date will just get you defensive responses from the Perl 6 folks....

I can give you the past 24 release dates for Rakudo Perl 6, and I can give you the next dozen--probably more. Pick one of those 36. Pick all of them. Don't pick none of them, because they're all Perl 6 release dates.

Does this mean that Perl 4 was never done in your sense of it? And similar for Perl 5?

Perl 4 is done now, in the sense that it's abandoned. Perl 5 isn't done.

If you can enlighten me, I'd appreciate it.

If you can tell me how to answer any or all of these questions accurately, I will give you your release date (for whatever you think "release date" means):

My preference is to avoid making public guesses where I don't have sufficient information and instead concentrate on delivering software that gets better and more complete and more usable and more useful every month. You have to evaluate 6.0 or 6.0.1 or 6.2 or 6.66 or whatever anyway. Why does it matter if one version has #25 and not 6.0?

In reply to Re^6: Will Perl 6 Replace Perl 5? by chromatic
in thread Will Perl 6 Replace Perl 5? by aecooper

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.