All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

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 har

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