Well, there are things that take way too long and come in way over budget, such as Boston's Big Dig or the Sydney Opera House. Often you hear the complaints because they are justified.

Perl 6 generated quite a bit of excitemenat at first and had a tremendous amount of progress through the RFC process. Now it's over five years later. I don't think it's unreasonable for people to wonder what's going on. We might not know the answer, but we also know that things took a lot longer than everyone expected.

The problem comes in when people try to ignore valid questions about the timeline. We can't just pretend that everything is going exactly as we planned because it didn't happen like that.

--
brian d foy <brian@stonehenge.com>
Subscribe to The Perl Review

In reply to Re: Building Perl6 by brian_d_foy
in thread Building Perl6 by duff

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.