Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

You'll be happy to know that Jesse Vincent has now stepped in as the project manager for Parrot and I'm the temporary grant manager for the project. Having a technical lead doubling as the project lead can create tremendous difficulties for large projects. Fortunately, Parrot is back on track and while there are certainly obstacles to overcome, we now have a set of milestones for the project and funding from NLnet.

I've also read Dan's comments and agreed with some, disagreed with others. I know that many are frustrated by the pace of Perl 6 development and I am too. However, in building and designing a project this large by using primarily volunteer labor, it's still amazing how far the project has come.

Cheers,
Ovid

New address of my CGI Course.


In reply to Re^2: Dan Sugalski's Parrot Post Mortem by Ovid
in thread Dan Sugalski's Parrot Post Mortem by Limbic~Region

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.