Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
You aren't alone. Check out RFC 28. I've been reading the p6-language list, too, and the impression I've been getting is that most people largely agree with you that the language shouldn't be changed as much as extended. Deprecated uses aside, I expect very few well-written scripts scripts will break during the transition, since there's such a huge population of functional scripts out there which the Perl 6 developers can't afford to break for the sake of cleaning up the source.

That being true, you won't have to learn anything new if you don't want to. But that's true now: very few Perl users know everything about p5 that there is to know. That's one of the great things about Perl: it's learning curve is as steep as you want it to be.

No matter what, your concern is premature. Until v6 has been proven as a solid platform, there will still be community support for the 5 series. The rough timetables I've seen project completion within about 1 1/2 years, but getting through the bugs for a full overhaul will require some time more. So you can keep using Perl for at least that long without needing to learn a thing.

Overall, I don't think anyone is going to lose out during the change. There are a lot of good reasons for reimplementing the interpreter, but the language designers seem determined to keep it accessible to its current fans and new users alike.

In reply to RE: Ripping out Perl internals in Perl6 by athomason
in thread Ripping out Perl internals in Perl6 by jjhorner

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?

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

How do I use this?Last hourOther CB clients
Other Users?
Others romping around the Monastery: (5)
As of 2023-11-29 08:19 GMT
Find Nodes?
    Voting Booth?

    No recent polls found