我应该选择 ActivePerl 还是 Strawberry Perl 呢？

After having used both for years, I'd say, for me at least, Activeperl is a much more convenient choice. The ppm-Installer included in Activeperl allows you to add alternative ppm repositories which will give you access to almost all useful perl modules available on CPAN - but prepared and tested for windows. This was for me, in the long run, a much better (and more robust) choice. Even for the windows version of the Apache http server, there is a precompiled mod_perl (2.0.4) ppm available which will (did for me) work out of the box with Activeperl 5.12.1 and Apache 2.2.15.

I think I dropped Strawberry after trying to install DBI + DBD::mysql on Windows 7 (which is a no brainer in Activeperl, just click on the ppms and choose install).

But maybe that's solved by now. And maybe one can choose the directory where Strawberry gets installed (I couldn't).

BTW: for compiling your own Inline or XS stuff, just install the MinGW compiler by ppm (I didn't do that but it looks interesting).

Regards

rbo

Addendum: after reading the comment below, I checked Strawberry Perl again and it's now possible to change installation directory, which is a denoted feature of the 5.12.0 release (which is the actual version). This would solve one important (imho) disadvantage of Strawberry Perl (compared to Activeperl).

If your design your application right, it shouldn't matter which you choose.

A big point might be the versions of various modules that each can provide, or not provide. PPM packages can lag behind CPAN releases, but if you aren't careful, bleeding edge CPAN releases can break backwards compatibility. Furthermore, sometimes there will be PPM packages for things that just won't build properly under Strawberry (though this implies that the module is poorly designed more often than not).

Just be aware of the versions of any modules you use, and you should be fine, regardless of which you choose.

Strawberry Perl uses CPAN, which means that you are up to date as far as modules are concerned. When things are added to CPAN, you have immediate access to them. Strawberry Perl also comes with MinGW which means that Strawberry Perl can use quite a few XS modules directly from CPAN without any modification. The MinGW distribution comes with gcc, make, ld and other tools to help you build modules. I think Strawberry Perl also comes with a few modules that let you install PPMs (Perl Package Manager files).

ActivePerl installs modules using its own format called PPM (Perl Package Manager). The official repository is hosted by ActiveState. You can find PPMs for most of the popular modules so you shouldn't have any trouble unless you are looking for an obscure or really new package (so bleeding-edge stuff won't work because PPM usually lags behind CPAN). Although easier to install than CPAN modules, PPMs are specifically created for Windows and so some CPAN modules will not work (because they do Unix-specific things).

I have used both before and it seemed to work for most cases. But I lean towards Strawberry Perl because the environment is closer to Unix and so there are not many incompatibilities. On the other hand, ActivePerl is made for Windows and so it works with Windows very well.

Another option is to install Cygwin and Perl that comes with Cygwin. I have done that before and it works reasonably well. You also get access to CPAN.

Pick what you think works best for you.

Strawberry is more Unixy in its approach, and I have been always very happy when I've worked with it.

ActiveState, however, due to its custom package management system, has been a colossal pain when I've worked with it. This matters when you're in an enterprise environment.

For just messing around, IMO, Strawberry is better. /subjective

Amplifying just a tiny bit on Vivin Paliath's helpful answer:

AcitveState / PPM pros: If there's a PPM for your version, it's going to work, and simply.

ActiveState / PPM cons: There's not always a PPM, or at least not always an up-to-date one.

Strawberry / CPAN pros: Your repository is CPAN, not a bunch of binaries maintained by third-parties. You have new modules the moment the author releases them, and you're using the build system that the author intended.

Strawberry / CPAN cons: Not everything is guaranteed to build perfectly with the Windows tools.

Strawberry / CPAN mitigating factor: The Strawberry devs try really, really hard to make sure that everything goes smoothly and that as much of CPAN as possible is available to you, and when modules are identified as trouble spots (difficult to build on Windows, but required for other popular modules/apps), they'll either work with the author to get the module fixed so that everyone can install it, or in exceptional cases, apply their own fixups and bundle the module with Strawberry or Strawberry Professional.

My preference is with Strawberry. I appreciate what ActiveState is trying to do, but I think it's a bottleneck in the development process. They were necessary before the community got together and built Strawberry to bring Windows into the "first world" of the Perl ecosystem, but they're not necessary anymore.

In a perfect world, I'd choose debian-interix or pkgsrc-interix perl (not the ancient Perl that ships with Interix/SFU/SUA) since it provides the most POSIX / UNIX -like system (including real copy-on-write fork, not windows fork emulation from Cygwin). I have in the past (and it is installed on Windows machines here), but not everyone can / will install SFU/SUA just for Perl. In those cases I'd recommend ActivePerl, primarily for the interface's familiarity to Windows users (PPM graphical shell versus CPAN) and its integration with the Perl Dev Kit (PerlExe, PerlNET, PerlSvc, and friends). Also, contrary to what others have answered, you can use CPAN (and the CPAN shell) with ActivePerl (though it does involve installing the necessary dev tools via PPM first) if you need it.

ActivePerl excludes tons of modules from Community edition and building them under Windows is a real pain.

Also, they would let you download and use only latest editions for free. Everything else, like access to 5.8.8 or to earlier version of modules is either Business ($1000/year/server) or Enterprise edition (per quote).

Both are great and work the same. Strawberry is known for being able to build XS modules, but you can do that with ActiveState too if you just install the Visual Studio SDK (or the free express version).

For that matter, if you have access to Visual Studio, the best you can do is to build Perl from source (it's pretty easy if you read the README) and keep building your modules with the same compiler. That's actually a better idea than having a mixture of compiler/modules.

One thing you have to consider if using ActiveState: If you install it on a server facing the internet, then you are required to buy a Business license ($1000/year/server as noted by Ron Warshawsky). It doesn't mean it won't work, it's only a matter of being a requirement in the EULA. Many people don't know this and have it installed on internet-facing servers without buying the corresponding license.

If you are using the box.com client to sync files, then you probably want (at least at the moment) to go with Strawberry Perl. The ppm executable conflicts with one of the Box.com DLLs. The gui will not start at all (yielding a Windows message that the "perl ... interpreter has stopped working".) I have also had intermittent problems using the command line version of ppm when the Box.com client is installed.

If Larry Wall uses Strawberry Perl so should you. ;)