The Rakudo-ng change was a deliberate decision among Rakudo developers to improve infrastructure code and to make the project stronger in the near term. Not every line of code is fungible; the old code was far from compliance with the standard Perl 6 grammar and -ng is much closer. The old code made certain features difficult to implement; the new code already handles things like laziness and lists much more correctly. The old code was slower; the new code is measurably faster.

The status chart is a little bit misleading as well. It doesn't show the value of the features, nor their difficulty of implementation, nor the particular features you or anyone else needs to use Rakudo * for your own purposes. If the status chart had updates over the past week and a half, you'd also see that test reclamation is a lot faster now than it would have been with the old code.

In short, the -ng changes were deliberate, and if that breaks your heart, you should talk to the developers as a whole in #perl6 on irc.freenode.net for their perspective. (Though I don't recommend you saying "Why did you break things? Aren't you going to miss your goal? Did you ever think of not making changes?")

In reply to Re: rakudo-ng branch by chromatic
in thread rakudo-ng branch by Anonymous Monk

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.