Okay there is a release of parrot every month, but that provides no prove that perl 6 is not a vaporware.

Parrot releases have included working versions of Perl 6 under development for years. I've had working Perl 6 code for years, in public, running on versions of Perl 6 developed in public and released in public.

How many more years you have to fight others with words instead of codes - a final release of perl 6 if there ever will be one?

There will be a release of Perl 6.0.0 when the people working on it consider it sufficiently featureful and stable that it deserves that number. The date of that announcement depends on several factors, most of them dealing with "When sufficient people have done sufficient work."

This is how community-developed software works. You've had the ability to download the code for Parrot since 2001 and the code for Pugs since 2005. You can check on their progress at any time you want. We develop everything in public, and we've even published the minutes of the Perl 6 design meetings publicly for at least a year. We don't have anything to hide.

I'd like to see Perl 6.0.0 released very soon, but in the past several months we've made solid progress on it -- despite our resource constraints -- every week, and almost every day in the past month.

Again, we have nothing to hide.

Feel free to call that vaporware if you like, but I'm proud of what we've done with as few resources as we have, and I'm really not sure what else I can do but point out that we've had working code for a long time.

If slapping the "final" tag on something makes it non-vaporware in your eyes, then I believe that's a ridiculous and meaningless metric. There hasn't been a final release of Perl 5 yet -- or Perl 1. The only software that meets your standard is TeX, and people still patch that too.

In reply to Re^4: Modern Perl and the Future of Perl by chromatic
in thread Modern Perl and the Future of Perl by chromatic

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.