It's unclear to me how P6 was a harsher environment for core contributors than P5 could have, would have been attempting to do similar things against the grain of a fairly ossified culture and spec by tradition; not to be pejorative; I have only praise and gratitude for all porters on all projects; they make my development life possible. It seemed like there was just as much community resistance and apathy for P5 forks as there was for P6.
From outside the Perlsphere Perl5 is largely considered a dead end and sub signatures and such wouldn't have altered that perception because it's a brand and application/library problem more than a language problem. If we're talking about wasted energy, there is a legitimate case to be made that it's what all Perl devs are expending since there are several good alternatives outstripping Perl in marketshare, new features, and problem domains. Again, that's devil's advocate. I love Perl and only code because Perl exists whether or not it's a cul-de-sac in which my career may be forever parked.
-
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.
|