in reply to Prefer Pure Perl Core Modules

I'm assuming you're still working in an environment that uses the customer's OS version of Perl.

For our (large) product, I insisted we build and bundle our own Perl (along with a carefully selected set of stable, well-respected CPAN modules). Had I been ordered instead to use the system Perl, I'd have used Perl only for smallish Unix shell scripts - and, like you, would've avoided non-core CPAN modules like the plague. That is, we'd probably have written all of our large complex components in C++, not Perl.

I might add that in our bundled Perl, we only bundled large, solid CPAN modules, like DBI, not small convenience modules, like File::Slurp. I'm happy to avoid the dependency cost by rolling my own file slurper, less keen to roll my own DBI. :)

See also the "Dependencies" section at Writing Solid CPAN Modules.

Update: As an aside, I stumbled upon RFC: Private CPAN In A Box by Perl::Critic creator jthalhammer (where he relates his experiences building private CPANs, aka Darkpans, for customers; RPM Package Manager was also mentioned).

Replies are listed 'Best First'.
Re^2: Prefer Pure Perl Core Modules
by Leitz (Scribe) on Jul 14, 2021 at 20:08 UTC

    Yes and no; mostly yes. I'm building an application to build my Perl skills, and one of the design goals is reduced complexity so someone else could use it. Building the app is pushing me to evaluate the trade-offs and giving me a chance to implement the good practices I've been exposed to for the past few decades. All five points are based on failures I have dealt with.

    There are a lot of development teams and environments, and a lot of different assumptions and expectations. For me, not depending on a lot of CPAN modules really works well. For others CPAN is quite useful.

    Chronicler: The Domici War (domiciwar.net)

    General Ne'er-do-well (github.com/LeamHall)

[reply]
      «…I'm building an application to build my Perl skills…

      A strange approach, with all respect. If I understood it right. I builded applications because I was in it for the money. Becoming better was rather a side effect. And a question of my professional ethics and my technical interests. Customers don’t really care about this. Best regards, Karl

      «The Crux of the Biscuit is the Apostrophe»

[reply]

        I learn best by coding through an introductory book and then working on a small personal project. Moving to a different language pushes me to learn things like accessing files, importing modules, etc. Often I'll do the same task in each new language just to see how that language handles the things I like to do.

        Chronicler: The Domici War (domiciwar.net)

        General Ne'er-do-well (github.com/LeamHall)

[reply]

In Section Meditations