Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chromatic (983)

  (email not shown publicly)

Blog Information [] Profile for chr0matic []

Journal of chromatic (983)

Sunday September 26, 2004
04:09 PM

Idle Core Thoughts

[ #21061 ]

Once a module goes into the core of Perl 5, it stays there forever, for good or evil. Having written tests for a chunk of core modules, some of that code isn't very good. (In 2004, we know a lot more about good Perl 5 programming than anyone did in 1995, so please don't read into that sentence more than I intend.) Some of the interfaces are terrible.

Will those modules ever go away? Unlikely. Backwards compatibility is important. Will those modules ever have interface-compatible replacements? Maybe someday, but how will you convince people to use them?

I wonder, idly, if every core module became dual-lived, distributed in the core and on the CPAN, if someone could write Bundle::CoreModules, keep it up to date, and the core could grow smaller.

Yes, there's still a problem with those people who compile Perl themselves apart from vendor packages, but I'd be surprised if those people don't have the technical saavy to download and install such a bundle somehow.

That leaves shops who refuse to install anything not distributed with the core. It's too bad that business stupidity isn't more lethal (to businesses).

There may be drawbacks I don't see right now, but the idle thought has a lot of appeal at the moment.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • It's too bad that business stupidity isn't more lethal (to businesses).

    I frequently hear programmers talk longingly about how their competitor's products are so much more professional and must be better written. However, I've sometimes had a chance to see the competition's code or talk to their developers and their developers have the exact same thoughts. Somehow everyone knows that the grass really isn't greener except when it applies to their own situation.

    The reason that businesses don't do a bet

  • Perhaps it would be worth seperating Core from Standard Libraries. Core is now so large that it might benefit from some hierarchal organisation into core (builtin and essential), standard and common.

    Looking at what is included in things like NMS and or required by commonly used modules like DBI would help categorise which modules should be organised where.

    It would also be nicer if openssl, etc were integrated into the core so that users had things like SSL, mysql, etc working 'out-of-the-box'.


    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;