Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Several important points.

First, even if perl 6 was released tomorrow (and trust me, it won't be) that's absolutely irrelevant--it'll be at least six months before the code has been beaten down enough to work out the bugs and get it in what I'd consder a production stable state. (I may have higher standards than other people) And, since you'll probably want another six months or so of small projects to work out the changes, it'll probably be a year before you'd want to consider it as a candidate for production code. (though the shaking out of bugs and playing with perl 6 time may be coincident)

Second, perl 5 isn't going away. There are many places that have perl 5.6.x, 5.005, and even 5.004 in production and active development. 5.004 is not new, and neither is 5.005. The version of perl you choose now will be fine for several years to come, and there will be new versions of perl 5.

Third, there will be a coversion tool, as well as a perl 5 front end to parrot, perl 6's back end. Who knows, given development efforts, we may well have parrot be a darned close to complete perl 5 engine before a perl 6 engine. Odder things have happend. (Though, for a variety of reasons, you won't see a parrot-backed perl 5)


In reply to Re: Resource protection and Perl 6 by Elian
in thread Resource protection and Perl 6 by pg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others contemplating the Monastery: (4)
As of 2024-04-19 23:08 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found