I'm not really sure I understand the purpose of your post. So if I miss, sorry.

I see Perl5 continuing to evolve. I see Perl6 as something quite different, that I would love to get my hands on a full implementation of, but am not holding my breath. If it ever happens I think they would likely coexists for a very long time. I think the best way that Perl6 could support Perl5 would be to just embed the existing perl5 interpreter. It could then run all existing Perl5 code and modules and interoperate without "shelling out".

I love some of the recent additions to Perl5. Though others--smart matching; given/when--haven't really floated my boat much.

Had I the wherewithall to lead or influence the next phase of Perl5's development, I would avoid the addition of new functionality and spend a cycle or two consolidating the existing code.

I think that there is much that could be done to improve the performance of subroutine calls, memory management, 'magic' handling, and unicode processing. Improvements in these areas would have a significant impact on everything else built on top. It could, for example, have a significant impact upon the performance of heavy, sluggish layers like Moose.

I'd also like to see some of the historical artefacts addressed. Things like input & output separators etc. being global rather than per-handle. Basically a clean-up of some of the many well-known existing Perl5 problems rather than the addition of new functionality.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

In reply to Re: What is best for the future. by BrowserUk
in thread What is best for the future. 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.