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.
  • The source code for the site is available. Commit access is easy to get. If you have a better design, nothing stands in the way of your improvements.

    • About ten years of lost progress stand in the way of improvements. Need I list the number of programming languages that came and went in that time?

      Thankfully I am not paying for any of the group developing perl 6, I would be pretty annoyed if that were the case.

      I can fix the webpage, sure. I cannot, however, fix the last 10 years of perl 6 debacle.

      • About ten years of lost progress stand in the way of improvements.

        Are you really meaning to imply that there has been no progress on Perl (5 or 6) for the last ten years?

        Need I list the number of programming languages that came and went in that time?

        Yes, I think that would be very useful to me.

        Pm

        • I'm not implying, I'm saying that perl 6 is to perl what "heaven's gate" was to Michael Cimino's directorial career.

          Perl 5 is great, but the sheer amount of resources that have been put into vapourwareperl6 is mind-boggling. And *please* don't point me to some project saying "you can use it now" because you *know* perl 6 is not production quality.

          • To clarify: There has been a little bit of progress on perl 5, namely perl 5.10. Perl 6 is a disaster, a train-wreck, a lot of sweat (including mine) lost forever in a project that should have been finished 8 years ago.
            • a project that should have been finished 8 years ago.

              On what do you base that timeline? Anything other than "That's what I would have liked?"

              --

              --
              xoa

              • http://www.nntp.perl.org/group/perl.bootstrap/2000/08/msg1185.html [perl.org]

                http://fr.linuxtoday.org/infrastructure/2000073101706NWCYSW [linuxtoday.org]

                http://www.perlmonks.org/?node_id=204115 [perlmonks.org]

                9 years later, Perl 6 has release managers engaging in casuistics over what "stable" and "done" mean instead of committing to an actual release date.

                • ... instead of committing to an actual release date.

                  If you know how to predict the availability, interest, and productivity of volunteers in a community-driven project, please review the Rakudo and Parrot milestone plans. I'm very interested in your answer to my (oft-repeated) question of how long it should take.

                  ... what "stable" and "done" mean...

                  I suspect you won't get consistent definitions for those from anywhere in software development.

                • Now I see the problem. You're conflating estimates from past project leaders with what "should" happen. This is an easy discrepancy to solve: Those past estimates were terribly wrong. Don't carry on the expectation that those estimates were correct or reasonable.

                  casuistics over what "stable" and "done" mean instead of committing to an actual release date.

                  If you can't define what "stable" and "done" are, then how can you expect an actual release date?

                  --

                  --
                  xoa