Thanks for your (relatively) straight answer.

Will that be fixed any time soon?

You don't seem to have noticed that, but the Rakudo Star releases are our attempt at fixing that. The "star" releases aim at providing modules, documentation and stability to the user.

Since the current development branch ("nom") has had quite a few regressions against the old master branch, we haven't made any new star release from it so far (though 4 months aren't that much, compared to the release cycles of many other projects). So people who use the star releases enjoy much more of the stability you seek. We'll take care to make the next star release as compatible with previous star releases as we reasonably can, though of course module authors and end users still have to track spec changes.

You seem to oppose the big rewrites that Rakudo has gone through, though so far I haven't seen you proposing any viable alternatives. I can see how annoying the breakage is that comes with such a rewrite, but we don't do them for fun; we do them because we see no other way to implement large-scale changes that need to be implemented in order to advance Rakudo. What would you do instead?

Perl 6 - second systems done right

In reply to Re^5: Waiting for a Product, not a Compiler by moritz
in thread Moose - my new religion by jdrago999

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.