Keep It Local
The article discusses the importance of keeping software dependencies local to avoid issues with remote package repositories becoming unavailable, using a real-world example of a dependency that disappeared from CPAN. It advocates for practices like vendoring dependencies or using local mirrors to ensure long-term stability and reproducibility of Perl projects.
Background
- This article is about a core tension in the Perl programming language ecosystem: the conflict between modules that use only Perl's built-in, no-nonsense features ("Keep It Local") and modern features that rely on external dependencies like the C compiler toolchain (XS, Alien, FFI).
- "CPAN" (Comprehensive Perl Archive Network) is Perl's vast repository of reusable code modules, analogous to npm (JavaScript) or PyPI (Python).
- The author argues that the push toward "modern" Perl — which often depends on heavyweight build tools — alienates beginners, casual users, and sysadmins who need simple, portable scripts that "just work" on any machine without compiling C code.
- This mirrors a long-standing debate in many dynamic languages: do we prioritize developer convenience (richer, faster libraries) or end-user portability (zero-build dependencies)?