Paul Graham has issued a new essay, The Hundred-Year Language, on what programming will be like in 2103. As usual it's an excellent read, and as usual he makes reference to Perl, as usual damning it with faint praise.

Language design is being taken over by hackers. The results so far are messy, but encouraging. There are some stunningly novel ideas in Perl, for example. Many are stunningly bad, but that's always true of ambitious efforts. At its current rate of mutation, God knows what Perl might evolve into in a hundred years.

What I'd really like to know is, what does he consider stunningly bad? The @_ parameter passing mechanism? Things that the Perl community considers failure themselves (e.g. v-strings, pseudo-hashes)? Absence of a lisp facility, such as macros? Difficulty of manipulating the op-tree at run-time?

Now, I'll admit that there are a number of things in Perl are at best a bit of a botch, but from there to something being stunningly bad...

I'll also admit I'm probably standing too close to see the forest for the trees, so you tell me, what is stunningly bad in Perl?

____________________________________________________________
Join the monks coming to YAPC::Europe 2003 in Paris, 23-25 July 2003.


In reply to "There are some stunningly novel ideas in Perl" -- Paul Graham by grinder

Title:
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, details, 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, summary, 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.