Perhaps what we really need to do is to declare that Perl forks along major versions, and that each major version is effectively a separate language, which was the stated intent with Perl 6. The catch is that Perl 5 was "good enough" to become very deeply entrenched in wide use. A later release is unlikely to be able to displace it, except, perhaps, by sabotaging the continued development of Perl 5, but we should be able to learn from the repeated disasters that PHP incurred when they did that with PHP 5 and PHP 7. A "Go 7" campaign trying to kill off Perl 5 as PHP did with "Go 5" to kill off PHP 4 is more likely to destroy Perl's continued viability entirely than it is to succeed.

(And PHP's "Go 5" campaign still did not really work — at the time, I was working at a small ISP that still provided Web host services. Know what we did about "Go 5"? We ended up keeping an ancient and long out-of-support server running to keep our customers' existing PHP 4 sites operational. All that obsoleting PHP 4 did was cause us to keep a server running at least half a decade past its "replace-by" date. We would migrate customers to the new server at no charge if they asked for a newer runtime or something other than PHP.)


In reply to Re^2: Amicable divorce by jcb
in thread Amicable divorce by ribasushi

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.