Perl 6 is no joke. For many years (2005-2015), I thought it would end up as vapourware or at least unimplementable, so I stopped following the project. But suddenly (or so it feels), there's a working compiler and one or two virtual machines that actually work. The language specification and the implementation are converging. Inline::Perl5 is genuinely cool and useful, even if neither it nor the compiler are "production quality". Now I feel the project will eventually succeed, even if it takes another 5-10 years to a full, optimised, mature implementation.
When it comes to books about Perl 6, the biggest difference to Perl 5 is that you can write a book based on the specification and it will remain valid and up to date for many years, even if the implementation changes. You can hardly say the same of Perl 5, which only has one implementation and no specification. I look forward to reading more Perl 6 books. I can't recommend it for production use at work, and I likely won't use it much in the next five years, but it contains so much that is new, interesting and Perl that I'll eventually make the switch. Just not yet.
-
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.
|