And that is exactly the problem with OS projects.

The next time you feel like complaining that Perl 6 or Parrot or whatever project doesn't take you seriously, remember that you agreed that no one gets to tell volunteers what they must care about. If you're not willing to do something, I see no reason why anyone who's actually do something should give your opinion one moment's notice.

You can still use Perl 6 and Parrot when they comes out though. We're just awesome that way.

Earlier you asked for an example of you asking someone to write code for you. I suppose vague, dark intimations that Perl 6 and Parrot are going to fail unless someone magically reads your mind and distills your ominous-sounding concerns into something concrete that somenoe can actually implement aren't precisely the same thing, but if you have something to suggest for Perl 6 and/or Parrot then why in the world are you whinging that no one will ever implement it and your Cassandra-like brilliance will go unnoticed and unlamented until too late?

I promise I won't ignore you if you actually say or do something useful... but will you just stop whining and arguing and do something?

In reply to Re^13: Slow evolution of Perl = Perl is a closed Word by chromatic
in thread Slow evolution of Perl = Perl is a closed Word by Anonymous Monk

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.