Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • Was this blog post just a troll against perl5 development? Confused.

    • It's a serious question.

      Very few people use Perl 6. Hundreds of thousands of people use Perl 5. Many businesses depend on it. (Yours does. Mine does.)

      Why are Perl 6's developers able to make and meet commitments to release software and Perl 5's developers unable to do so?

      There are many possible answers. Perhaps no one wants new releases of Perl 5. Perhaps it's impossible or infeasible to release stable versions of Perl 5. Perhaps publishing a ROADMAP or a rough schedule of Perl 5 releases is a bad id

      • by Matts (1087) on 2009.05.29 9:01 (#68842) Journal

        Well Perl6's development process is new, and thus nimble and agile. Perl5's is slower because it has a lot more history.

        Is it changeable? Probably.

        Is it totally broken? Not really, though I do wish to see 5.10.1 some time soon!

        A regular release is a nice thing to have, but it doesn't always create the most stable platform or the most confidence.

        It might interest you to note that SpamAssassin has the same problem right now - it's been forever since the last release.

        One thing I did think about with perl5 is that the number of required test platforms for all tests to pass is too high. It made me wonder if we shouldn't rely on vendors to fix issues with their platforms if they want the latest perl there. Such platforms would be: AIX, HPUX, Solaris, OSX, VMS. All of them are low-user platforms (with the possible exception of OSX, but they have a lot more money to throw at it).

        • One thing I did think about with perl5 is that the number of required test platforms for all tests to pass is too high.

          I've come to the same conclusion. Platform-specific porters there do great work that I often don't understand, and I mean no disrespect, but sometimes the delay between making a commit and getting sufficient feedback from one of those platforms to have confidence in that commit is exceedingly long. I believe that's a function of a low number of available porters.

          This problem seems to af