To some extent, the *::Tiny "namespace" addresses this. But I get the feeling that the real issue is that Perl has simply become bloated over time. If nothing else, there are probably quite a few modules in CORE that really don't need to be there to have a working install. Yes, they are handy, and if not part of CORE would have to be brought in from CPAN for many other modules. But some of the most essential modules for many applications are not part of CORE, i.e. DBI. I say leave some of those others out and let them come in when installing something from CPAN that needs them.
(This was almost exactly the stance taken with v5.20 with the removal of CGI from CORE.)
I stopped being able to do a perlbrew install of any relatively recent version of Perl on my hosting service because of execution runtime limits some time ago. My provider (a very popular one) limits command line scripts to only 15min before being shutdown. That means that to install a Perl with perlbrew I have to tell it to NOT run the tests, then come back and run the test suite manually. This is entirely due to the large number of modules in CORE now.
In reply to Re: Perl::Minimal -- the good, bad, and the ugly...
by boftx
in thread Perl::Minimal -- the good, bad, and the ugly...
by taint
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |