Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • > I can predict the day and date of Parrot releases into the next century.

    BTW, there's your hyperbole.

    I really would leave that point alone. One can predict all sorts of things, but who's to say they'll be true. Your prediction, should you actually do it, requires that you'd found a way to guarantee the accuracy of releases, to the day, after you are deceased.

    Also, there's nothing at stake. Now of course, if you were to specify a series of exact release days and dates stretching out for the next several

    • Also, there's nothing at stake.

      It's software. There's very little at stake anyway.

      Of course there are conditions to the prediction: Parrot must be a maintained project in 100 years and the current release strategy must remain (at least for the twice-a-year supported releases).

      Would you feel more comfortable if I predicted the dates of the next twenty four releases? We've hit our target dates within 24 hours for the last thirty or so releases; that's an easy prediction to make.

      • That would be great.

        Care to place a wager on whether or not you'll hit them all?

        • That would be great.

          Care to place a wager on whether or not you'll hit them all?

          That's not the point, at least in my perspective. With Parrot and Rakudo there is a consistent plan in place that indicates when the next release is made, pretty much to the day. I believe there has been one slip in Rakudo's release schedule of a few days (announced ahead of time).

          In stark contrast, the same thing cannot be said about perl 5.10.1, 5.12, etc. At this point I couldn't state with any certainty what the intended release data for any of those are to within a year (that fix for the performance regression in 5.10 would sure be nice), nor what the plans are beyond a 'statement of intent.'

          Speaking of, I have to agree with sigzero's point above; intentions (and statements thereof) are great, but concrete plans and progress are what matters in the end and are what we would like to see, not hand-waving and worries about compatibility issues with code we can only guess at.