Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Hopefully I've been able to understand your perspective in this exchange.

I don't believe you've ever understood my perspective. For example:

apportion moral blame?

Weren't you just complaining about twisting words?

I participated in mailing list discussions in the early years (I think 2001-2004 or thereabouts), read Piers' reports, that sort of thing. I didn't pay much attention to YAPCs. I mostly missed Audrey's 2005-2007 involvement. I don't recall seeing the estimates you speak of.

I was on the core design team from 2003 to 2011. I edited Piers's reports for Perl.com. I went to YAPCs. I pair programmed with Audrey in Toronto.

I took notes for every design and status meeting I attended for 8 years. (I counted once; there were enough words in those reports to fill multiple versions of the Camel.)

You will not convince me—and I will correct the record when you try to convince others—that the original delivery plan was anything other than 18 months, that that 18 months figure was repeated frequently, and that there were no serious or successful attempts within the project leadership to deliver a solid, reliable product within that time period.

The closest we came to that was Allison's push to stabilize and release Parrot 1.0.


In reply to Re^9: The Future of Perl 5 by chromatic
in thread The Future of Perl 5 by Laurent_R

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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (1)
As of 2024-04-25 04:08 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found