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.)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|