Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I disagree almost completely.

  • Perl 5 gained a tremendous influx of new people and ideas after the announcement of Perl 6. PerlIO, Perl QA, the Perl6:: namespace on the CPAN, the defined-or operator, locked hashes, assertions...
  • There have already been two "Perl 5 oriented Parrot" projects: Sapphire and Topaz. They were done much sooner in the sense that they've been long dead.
  • Several of the features you call "theoretical" have had practical benefit, some for decades. I don't understand where to draw a line between "adding proven features from other languages and a few new features is good" and "adding proven features from other languages and a few new features is good". They both read the same way to me.
  • I've met very few practicing programmers who could actually read code well.
  • It's way too early to complain about Perl 6 error messages when they haven't yet been written.
  • The original design of Perl was simple, if you had experience in Unix, sh, C, awk, and a few other languages you'd probably call "boutique".

I'm sympathetic to the fear that Perl 6 is hard to understand. I certainly haven't wrapped my brain around it, but it's starting to sink in over time. There are deeper consistencies you're not seeing yet, partly because the whole design hasn't emerged and partly because you're used to some of the quirks of Perl 5.

I just don't think the facts really support your other arguments, though.

In reply to Re: Re: Perl 6 is too complex by chromatic
in thread Perl 6 is too complex by Anonymous Monk

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

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others examining the Monastery: (5)
    As of 2018-06-17 22:30 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (107 votes). Check out past polls.