I would cautiously offer the frank opinion that it doesn’t matter, and for (at least) the following two very-frank reasons:
- Perl-6 doesn’t matter. If it ever does come to see the light of day, it will be, and it will be regarded as, “The Entirely New Language Also Coincidentally Named ‘Perl.’” If it happens to contain its own built-in database API, then it is even more insufficient than its erstwhile decade-old predecessor, which supports many by intrinsically supporting none. And let us be frank: do we actually need Yet Another Procedural Programming Language, even if we decide for some reason to call it, “Also Perl?” Methinks not.
-
There’s no money in it. Google didn’t actually do anything that it actually did for any other reason other than to steal away the need for royalty checks. Copyright arguments are being pressed into service, I think, because they seem to someone to be the best legal theory that they have come up with yet, whether or not they actually apply. If Google can sweep the wind out of anyone else’s incentive to pay money to Oracle for what Oracle did first, then Google will have succeeded. But Perl-6 isn’t even in that ocean. Perl-6 is very frankly nowhere. In any case, it is in no danger.
-
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.
|