Is there a reason, why rakudo should target many back ends?

The only worthwhile reason I've heard is "People want to do it." (Targeting multiple backends hurt Pugs more than it helped.)

Diversifying so quickly will slow down an already slow process.

Only if you assume that developer time, interest, and ability are fungible. Porting NQP-rx to .Net may attract people who have no interest in Rakudo on Parrot. Porting NQP-rx to LLVM may attract people who have no interest in Rakudo on the CLR or Parrot. Porting NQP-rx to the JVM may attract Larry Ellison.

In reply to Re^2: Backend diversity for Rakudo by chromatic
in thread Backend diversity for Rakudo 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.