Let's address the points one-by-one.

Database access is almost a must today
Is it? I beg to differ. For many jobs, database access is irrelevant. One of the areas Perl has been been used a lot, even before the web was something more than a handful of people cared about, is system administration. There, the typical job does *not* involve access to databases that are more sophisticated than flat ASCII files.

Besides, when the time comes that "databases access is a must", it'll be integrated in the OS. ;-).

Perl is a high level language
Not more than C, C ++, Pascal, LISP, or ALGOL. And they do fine without database support in their "core".
We have great modules like DBI and DBD.
Yes, and? There are more great modules on CPAN. They aren't included in the core either.

"Greatness" or "usefulness" is not a sufficient criterium for a module to be put in the core. The more modules you put in the core, the harder it is to maintain the core, and the slower perl development goes.

The perl core is already bloated with modules that do not have a place in the core - and that should not be taken as a reason to bloat it even more. IMO (and others shared that as well), modules should only be put in the core if they fit one or more of the following criteriums:

  1. They are tighted to the core, or a core feature, and are hence often version specific (for instance B::*, pragmes, IO::*).
  2. They are needed to build, test or install Perl (for instance, Test::*, ExtUtils::*).
  3. They are needed to fetch, build, test, or install external modules (for instance CPAN, MakeMaker, AutoLoader, SelfLoader).
The rest of the modules does not belong in the core. They are not needed.

Abigail

In reply to Re: Why Perl does not support database access through core modules? by Abigail-II
in thread Why Perl does not support database access through core modules? by pg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.