Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

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

My main objection to Perl 6 is that it will be mind-boggingly complex, both in semantics and possibly in implementation. It's not about new syntax, new object-oriented goodness, new regular expressions, new what-not; it's about all those together. I have read half a dozen Apocalypses, several Exegeses, and I cannot comprehend how anyone could understand the whole, much less how it's possible to implement it without errors.

Of course, the counterargument goes that you, as a programmer, need not learn everything, that you can use only a subset of the language. But that's not the point. Someone (or rather several someones) has to implement the whole wickedly large language, and even so that 1) the implementation and the specification match, and 2) there are no (engineering) errors (bugs) in the implementation. Will it be humanly possible? I'm doubtful.

On the other hand, I'll be probably among the early adopters once the first usable version of Perl 6 will be released. It contains a myriad of improvements over Perl 5, and a plethora of improvements over other existing languages, including Haskell and Lisp. I fully expect it to become a hugely popular language.

--
print "Just Another Perl Adept\n";


In reply to Re: What's wrong with Perl 6? by vrk
in thread What's wrong with Perl 6? by duff

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 lurking in the Monastery: (6)
As of 2024-03-28 15:27 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found