Nowadays, ActivePerl also supports user compilation of modules, including XS modules, and the PPM utility becomes a little redundant. This really was Strawberry Perl's niche originally that someone familiar with the Linux/Unix way of doing things with Perl would be able to use the standard Perl tools in building modules. Strawberry packaged the gcc compiler and 'make' along with Strawberry Perl, which allowed users to take advantage of the standard Perl toolchain in installing CPAN modules the CPAN installers, or just downloading the tarball, unpacking it, and performing the make, make test, make install mantra. This was because historically modules required the extremely elusive Microsoft utility, "dmake" to be built out, and if a C compiler was required (for XS modules, for example), it was even less likely that a given system would be equipped with the necessary tools. Years ago, ActivePerl packaged up many of the popular Perl modules into ".ppm" distributions that could be installed using the ppm package manager. I think many times it kind of goes along with the mindset of "Nobody ever gets fired for choosing to start a project using Java." In other words, it looks good on paper.įrom a practical standpoint, the primary difference between, say, ActivePerl and Strawberry has become less significant over the years. In practice each organization has to evaluate whether the peace of mind of a support contract, and the support it provides are things that they need. Nowadays one of the main reasons to be using it is the ability to buy a support contract, which mostly is there to satisfy PHB's and other managerial folks who sleep better at night knowing that when something breaks their bosses won't fire them for using a "community supported" version of Perl. Now we get to the interesting part of the question. Outside of your organization there are many who do use other flavors of Perl in production, many self-compiled/managed.Īll the scripting work I have done are Windows Test/Certification Servers which don't have any production apps running on them.Īre there any advantages of using Activestate Perl? Possibly within your organization that's true. Infact he stated that all the Perl Scripts running in production environment use Activestate. But a support contract is one reason that an organization may prefer ActivePerl. Not all organizations gravitate to ActivePerl - some self-manage, some use RedHat, etc. a lot of organizations prefer using ActivePerl because it has commercial support.Īssuming those organizations are purchasing a support contract from ActiveState, this may be true. I was told by a senior at work to start using ActivePerl on Windows. Re: Advantages of Activeperl vs Strawberry Perl
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |