over my years of development on parrot, pugs, and rakudo, i've become much less active in the perl 5 community. for example, i used to frequent perlmonks, but time no longer allows it. instead, i'm now quite active in the perl 6 community. historically, i'm not part of @Larry (the nickname for the perl 6 design team), and although i've been invited to attend the weekly design meeting, it was as a parrot and rakudo developer, not as a designer.

while developing rakudo, i felt the compiler was growing to a point where it'd be useful for folks to do day-to-day programming tasks, and have a little fun with the language revision we've been waiting so long to get. so, i started adding command-line options like -e, -h, -c and -v. rakudo became much friendlier to use, since i could check the syntax of a perl 6 script i wrote, and find what revision of rakudo was failing to parse or run a particular script so i could submit a proper bug report.

then two things happened: it bothered me that there was no spec for the command-line so i couldn't really implement anything more than what i'd done already, and ian hague donated a pile of money to tpf for perl 6 development. i decided to apply for a grant to define and implement the perl 6 command-line syntax, and my grant was accepted. now, i'm in the process of designing a working draft of Synopsis 19, describing the command-line syntax, and soon i'll be writing tests and implementing it in rakudo. all this is being done in a public repository (pugs) with a liberal commit policy, and is being discussed on open mailing-lists and irc channels. i've gotten quite good feedback, a few nice ideas, some excellent questions, and some corrections this way. i wouldn't succeed at this task if not for the support of these helpful folks, too numerous to mention.

i became part of the perl 5 community the first time i wandered online for help (probably sometime late in 1996). i've never submitted a patch to perl5-porters, so although i'm quite adept in using perl 5, i don't come from the perl 5 illuminati. changing my focus to perl 6 development has given me a great education at little cost (just spare time), and i'm now able to give back by designing a crucial feature of perl 6 that countless people will use every day for years to come. if my story isn't a shining example of a "community rewrite" of perl 6, i don't know what is.

~Particle *accelerates*

In reply to Re: How much is Perl6 the community rewrite of Perl? by particle
in thread How much is Perl6 the community rewrite of Perl? by zby

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.