Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Yes, compared to those who don't know any Perl, "P5ers" have, on the one hand, a head start (the many identical aspects of P5 and P6) and, on the other, the frustration/confusion that arises from changes including many seemingly random subtle ones.

Some things to consider:

  • I've witnessed (and occasionally participated in) continual discussion over the years of established aspects of Perl, from the spelling of keywords and various idiosyncrasies to muscle memory and common P5 mental models, and of minimizing and mitigating the impact of changes between P5 and P6.

  • This isn't just theory. Many P6ers are also P5ers and clearly don't like being confused or frustrated when switching between the languages. These P6ers are dogfooding the switching experience and improving it as they go.

  • The compiler is helpful. There are many warning and error messages that reflect knowledge of P5isms, their corresponding P6isms, and how to help folk switch.

  • Several folk have written P5-to-P6 doc, eg Moritz's P5 to P6 articles. Unfortunately a lot of it is out of date which of course increases the sense of uncertainty. :(

  • There are P5 and P6 evalbots on #perl6 and #perl6ers are eager to help anyone wanting to learn P6, including skeptical P5ers. (This is the primary antidote for the previous point.)


In reply to Re^4: sort +*, @array by raiph
in thread sort +*, @array by raiph

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 examining the Monastery: (4)
As of 2024-04-19 21:05 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found