use Perl

• Don't you think this is counterproductive? (Score:1)

  by Alias (5735)

  
  Due to the continued rapid pace of Rakudo development and the frequent addition of new Perl 6 features and bugfixes, we continue to recommend that people wanting to use or work with Rakudo obtain the latest source directly from the main repository at github. More details are available at http://rakudo.org/how-to-get-rakudo [rakudo.org] .
  

  This release announcement reads to me as...

  "We've released the new version of Rakudo. Don't use it. If you're sophisticated enough to have and use git, pull from version control, set up
  • Re: (Score:1)

    by chromatic (983)

    If people are interested in Perl 6, is it really SO bad that they are running 1-4 weeks behind the bleading edge?

    No, but they're probably missing out if they're a week behind the bleeding edge. The pace of development can be astounding. Ask anyone who's used it this year.

    Why bother doing releases at all?

    So that code regularly reaches a wider audience of users and potential testers and contributors.

    So that people don't have to track trunk.

    So that people have a regular stable distribution of Rakudo at
    • Re:Don't you think this is counterproductive? (Score:1)

      by mpeters (5802) on 2009.05.29 7:03 (#68840) Homepage Journal

      I'd add one more to this list.

      + So developers can get practice at making releases before people start to depend on them for critical work.

      Reply to This

      Parent

      • Re: (Score:1)

        by chromatic (983)

        I forgot that one; thank you. It's more important than my omission makes it sound! If making a release is so easy and boring that any of a dozen people can do it with an afternoon's notice, any of a dozen people can make a release to fix a critical bug. We all hope that's not necessary, but we can spend our time focusing on the important part of that process.