in reply to
Re: Top Seven (Bad) Reasons Not To Use Modules
in thread Top Seven (Bad) Reasons Not To Use Modules
I tend to scoff at the "no installation needed" at a day and age where users have machines infested with Java and Flash installation (often 2 or 3 of them) as well as other runtime environments.
But there's a large difference between a user machine (which, nowadays, typically gets used by a single person, can be easily replaced, and if down, only affects one person) and a server that is important or even critical for the operation of a business.
Having said that, I've worked on servers that have multiple Java installations as well - and, IMO, that was good. An application that needs Java, and comes with everything needed to run Java is so much easier to install than one that doesn't. If the app comes with Java, it will always have the right version (and if it doesn't, I can blame the vendor of the app) and will not conflict with other apps needing Java. And, IMO, that's the way to deliver (large) Perl applications as well. Include everything. All modules you need. Consider including perl itself as well (because even if your target OS comes with perl, it may not be the right version or it may be compiled with the wrong options).
There is no One True Rule, despite the many claims here, and elsewhere.
That, I fully agree with.