Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

comment on

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

You should not be thinking about Perl6. It's deeply interesting. It's moving forward well. It's not ready. So unless it's to satisfy curiosity or to contribute or to gamble on the future to get ahead of the curve, ignore it. Perl (5) is not going to disappear. Its releases have been like clockwork for years. It's as stable and useful as any language and likely to remain the leader in things like regular expressions and Unicode support. Perl6 will have nearly zero influence on Perl5 until and if it becomes stable, complete, and as fast. This is not going to happen next year or the year after and it may never happen at all.

Perl5 is a fantastic, vibrant language, with a rich ecosphere, actively moving forward and it will be for the foreseeable future. If you like it, jump back in with both feet.

Update: did not realize I'd klept "vibrant" from Corion. :P Regarding Python: the 2/3 split being installed and competing with shoddy include/discovery code on boxes in install scripts is what led me to wonder how anyone likes it at all. It's been nothing but a PITA to me and from an accidental user's perspective it seems like a hot mess full of bad practices and assumptions. Perl, Ruby, and Node.js toolchains have all been kinder and saner for me.


In reply to Re^3: Should I come back to Perl? by Your Mother
in thread Should I come back to Perl? by jekyll

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 imbibing at the Monastery: (6)
As of 2024-03-28 14:13 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found