Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Let me be frank:   please stop calling this thing “Perl 6.”   Call it Rakudo ... present it as a new language.   (With a sexy trendy name.   Do the whole faux-Ninja thing, to appeal to the twenty-three year olds among us who still love spending all day and all night hacking software.)   ;-)   This is IMHO a much better positioning of this project at this point in time, and not a criticism of the effort or its extreme lateness.   In support of this notion, I offer these points three:

  1. If it’s source-code compatible with Perl, it’s not better, and it is now at cross-purposes with itself.   The internal complexity of the system shoots up, and stability goes down.   Various other projects, including ADD 1 TO COBOL GIVING COBOL., have encountered this issue before.   You really can’t change an existing language that much and call it the same language.
  2. If it’s not source-code compatible, then “it is a different language,” and everything of significance is going to have to be ported, so the CPAN library effectively splits.   Very well, then:   let it split, and do it cleanly.
  3. There is a mammoth installed-base of Perl5.   These installations consist not only of the interpreter executable, but also the CPAN libraries.   The possibly major changes to these libraries which might be attempted in order to accommodate Rakudo might well de-stabilize them, causing significant business problems for installations which have no interest in adopting Rakudo at this time.

If Rakduo, called Rakudo, is deployed in a parallel but separate track, the cost/benefit analysis holds up.   If, instead, it disrupts existing installations in any way, it produces cost without benefit.   Perl has a history now.   It has a legacy to support.

Once again, this is not a flame; this is a Meditation.   I invite equally cordial comments; not just +/- votes.   What do you think in response to my comment, and why or why not?

In reply to Re: Perl 6: Managing breakages across Rakudo versions by sundialsvc4
in thread Perl 6: Managing breakages across Rakudo Star versions by raiph

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others contemplating the Monastery: (5)
    As of 2017-10-17 02:29 GMT
    Find Nodes?
      Voting Booth?
      My fridge is mostly full of:

      Results (218 votes). Check out past polls.