Perl 6 has, with great sadness on this reviewer's part, been relegated to the hall of things that were too early, or perhaps too good(?), for their audience.
In 2002 it all seemed so promising. Linux was enterprise class and the steady Perl 6 list wars about -> and _ only showed the passion, the vast fuel ready to drive this motor to the edge of space. Who could have forseen that just 1 year after Parrot, the underlying bytecode compiler for Perl 6 et al, was declared in production release, Microsoft would buy Sun while simultaneously moving Java to the GPL and releasing the SlapJack IDE including the source code for Longhorn and Steer!. The U.S. Supreme Court's landmark "Gates v Logic" was the final nail in the coffin, legitimizing the newly created U.S. Department of Coding and Software which requires a one billion dollar license to sell software in America and abroad. What a difference a day--and 400 billion dollars of cash reserves--makes.
Let us all observe a moment of silence while Perl 6 takes its place beside BeOS, NeXTSTEP, Betamax, and Linux on the long list of should-have-beens.
-
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.
|
