IMO, the Perl CORE is too large anyway and with CPANs almost universal ubiquity, it is much easier to update modules outside of the Perl core and still deliver them to a user. p5p cannot (and does not want to) maintain that many modules.
This is partly a reaction prompted by the times when Perl releases were rare and far in between. A module that only existed in the core back then did not get bug fixes until a new release of Perl. At least nowadays most modules are dual-lifed, that is, they exist within the Perl distribution and on CPAN so they can see far more frequent releases than Perl itself. This is a lesson well-learned, for example the Python core includes some modules that can only be upgraded by upgrading Python itself - the csv parsers are an ugly example of this.
I think that Module::Pluggable (among others) only got into the core because CPANPLUS relied on it, and with CPANPLUS gone the justification for having that module in the core is also gone.
Of course it would be much nicer to have a "batteries included" version of Perl, and Strawberry Perl for Windows is quite close in that regard - it also includes XML::LibXML, which is not XML::Twig, but it's close.
In reply to Re: About the CORE and the history of Module::Pluggable
by Corion
in thread About the CORE and the history of Module::Pluggable
by Discipulus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |