in reply to What modules should be added to the corelist?

In a world where we often work by targeting containers, and also often use tools like Carton, I don't see a big advantage to growing the core distribution. In fact I see doing so as being disadvantageous to the container paradigm. A nice slim distribution, with simple means of either bundling or pulling down what is needed makes more sense, I think.

To some degree I think that the existence in the core of modules that aren't needed for building and installing Perl and installing modules is mostly a result of inertia and a desire to maintain backward compatibility. I don't know if Hash::Util is used by the Perl install process, or to facilitate installing other modules. If not, maybe it's a candidate for exclusion from the core, except that we're kind of locked in to avoiding breaking changes. CGI was dropped from the core not only because it wasn't needed there, but because keeping it seemed like an endorsement of an antiquated programming model.


Dave

  • Comment on Re: What modules should be added to the corelist?

Replies are listed 'Best First'.
Re^2: What modules should be added to the corelist?
by Anonymous Monk on Aug 17, 2019 at 06:04 UTC
    CGI was dropped from the core not only because it wasn't needed there, but because keeping it seemed like an endorsement of an antiquated programming model.

    The CGI module is a GUI toolkit for web apps. It was added to the core because the web is important. Dropping it, as the web's relevance grows, makes sense to me. No not really. I would keep that for full backcompat, and add something like Mojolicious::Lite for modern web apps. :-)