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.
  • Actually, I don't think you get it :)

    You're not diversifying. You're un-difersivify. ActiveState was diversity. It was a different source for Perl and for modules. Now you've made Perl come from the same source everyone else uses and download modules from the same source that everyone else uses.

    I think it's that diversity which hurt Perl for a long time on Windows. Instead of having Srawberry Perl ten years ago, we let ActiveState have that domain. With ActiveState, no one had any incentive to work that hard to make Perl installation on Windows as easy as on Unix.

    As for the rest of the stuff Andy says, well, it's nothing new, and it's something that goes in cycles. People work independently, then they form groups because its easier to get things done. Wait awhile, and they think the group is holding them back, so they want to be independent again, to restart the cycle.

    Just do good work and don't worry about the domain names. :)
    • I hereby note that Strawberry supports CPAN, direct tarball installation via pip, PPM modules/repositories, PAR archives, and the .P5I install scripts, both locally and from URIs.

      Instead of just PPMs from a single repository.

      Voila, diversity :)
      • I haven't tried pip, although I have used Strawbs.

        Direct installation from CPAN is a great relief, because without it I was thinking of donating to you $1000 for a build farm and pre-compiled repository, and now you're 'saved' me the money!

        As for the command line app, instead of cpan, we're surely call it peter.pan, except neither of our names is Peter :-O.
    • To be fair, it was a huge advantage that there were people interested in Perl who knew how to write code for Windows and actually did.

      I've abandoned a few projects because I couldn't get them to run on Windows and was sick of Windows users complaining but never actually trying to help fix things.

      • I'll note that the "people interested in Perl who knew how to write code for Windows and actually did" group doesn't really include me.

        I am interesting, and I prefer to "actually do", but really I don't know how to write code for Windows.

        I muddle through in a couple of areas (like File::HomeDir) but mostly I just bug OTHER people to make their stuff work on Win32. I mean, I didn't create the original Vanilla MinGW setup, I didn't create the original .exe builder, and I didn't do much of the toolchain portin
        • The the beauty for me is that, once set up, I do almost none of the work, and still get a ton of the credit :)

          What I am saying is that -- without taking credit from anyone working on Vanilla, Strawberry, or Chocolate Perl -- ActiveState still deserves tremendous credit for making it possible to run the same code on Windows as Unix and Unix-like systems.

          I'll push toward the front of the line for criticizing ActiveState's technical decision to push backwards compatibility and kill all hopes of getting m

          • On this point, I agree completely.

            They deserve a lot of kudos for the port, but in the last 5 years they've failed to live up to their previous standards in my opinion.