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 really liked the description you gave during the Rakudo BOF on YAPC::EU. Maybe we should use it as a subtitle of Rakudo:

    Rakudo, implementing a useful subset of Perl 6

    Later I thought that by using the name Rakudo we can actually avoid the Perl 5/6 trap and the "when is Perl 6 going to be ready?" trap.

    Maybe the disconnect between Rakudo and when is "Perl 6 going to be ready" could be increased by giving small and increasing version numbers to the Rakudo releases - even starting by the next one - and having a Rakudo spec coming with it.

    You could use 0.20 or even 0.020 instead of the upcoming release 20 of Rakudo giving enough version numbers before you reach the magical 1.00.

    You could also start this process from April next year though I think the sooner the better.

    Each version could come with its own specification - basically a subset of the Perl 6 specs that covers that version. We could embed some marks in the Synopsis (or have those marks externally, similar to the smart-link in the test-suit) and have some code extract the relevant parts from the specs.

    We could use marks with the planned version numbers when those feature will be implemented. Making it easier to draw up a roadmap.

    This way people can start using Rakudo 0.20 or whatever version number, and know what to expect.

    --
    • If people are going to put thought and effort into understanding if Rakudo is useful for them, I'd like them to do so based on the ratio of planned and implemented features important to their work, not on lengthy explanations of magical version number schemes.

      It would be a shame to fall into the magical version numbers trap while trying to avoid the magical version numbers trap. ("Rakudo 0.2 in April? Those fools! Can't they release software? Everyone knows that software isn't usable for anything until