It is definitely a mess. Even with Python, a language that's much more modern, between its current stream and the future P3K stream, there is a need to break the backward compatibility. To entertain P5 in P6, the penalty will become clear very quicklya, and it certainly makes P6 much less attractive in lots of people's eyes.

On the other hand, to look at this from a higher level, the opportunity of success is not very good for Perl 6. With Python and Ruby around, less people will appreciate P6, which is similar and less sophisticated. P6 is taking too long to deliver, and the world does not stop and wait, the moment P6 comes out, it is probably obsolete already in many ways.


In reply to Re: Perl 5 <-> Perl 6 compatibility: a benefit or a mess? by Anonymous Monk
in thread Perl 5 <-> Perl 6 compatibility: a benefit or a mess? by citromatik

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.