But it's clear that Perl 6 is going to get a lot faster in 2013.
... based on microbenchmarks of a language that isn't Perl 6?
No. You've picked up on what I consider a point of interest rather than the big picture.
The outlook for Perl 6 speed improvement in 2013 is based on many factors:
- I mentioned several factors in my post. For example, Larry Wall declaring speed to be the #1 blocker of adoption in November.
- There are other factors I didn't mention. For example, Rakudo is sufficiently complete that the existing core hackers are fairly free to focus on other things, and speed is increasingly becoming a priority for Jonathan and Moritz. Furthermore, as Moritz notes, the Rakudo toolchain has reached the point that non-core-hackers are successfully hacking on AST generation and NQP to improve speed (with the nice side effect of leading them toward being new core hackers). I could continue but I recommend anyone interested visits #perl6 and asks questions.
As for "a language that isn't Perl 6" I'll point out that NQP is basically a small subset of Perl 6 (NQP stands for Not Quite Perl) and Rakudo compiles to NQP. So if NQP gets faster, Rakudo Perl 6 gets faster.
-
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.
|