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.
  • In November/December, I built an alpha release of "Vanilla Perl 6" (combining Parrot and Rakudo).

    I found it to be uninstallable (because it hard-coded all the filesystem paths at compile time which made it almost impossible to make an installer) and it leaked memory so fast that most simple test benchmarks I created consumed more than the 2gig process limit after running for a few minutes.

    I concluded that the implementation was not sufficiently stable for me (as a person who doesn't know C) to do anything u

    • Yeah, I don't know .. I don't think it's the responsibility of the upstream to maintain the distribution packages, too... looks like Allison is maintaining the parrot deb anyway though!
      • It's the responsibility of the upstream to make it both possible and (ideally) easy for the downstream to package it.

        For your new project with no existing downstream channels, it's a fairly basic thing to engage with the people most likely to be your downstream and go out of your way to make life easy for them.

        And for channels without an existing community to do any of the work (like Win32) it's probably going to mean doing it yourself, at least for the startup period.

        Maintaining the channels are one of the first areas you are going to get contributors for, once the users at the other end start to depend on it.