Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

X is better than Y 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • For a long time, the only game in town was Matt Wright, and Matt's scripts got a lot of airplay and mindspace. But the NMS project rewrote them, and now there's no reason to use Matt's scripts now that NMS is out. But that doesn't stop people from continuing to suggest Matt's stuff, only because they don't know any better.

    MySQL is there mostly from inertia now. Other than legacy compatibility, there's really no reason to use it. So for new starts, I'm trying to help set the record straight, in the NMS

    --
    • Randal L. Schwartz
    • Stonehenge

    • That's a terrible analogy. It's no secret that Matt's scripts are poorly written (is MySQL poorly written?), with no support (does MySQL have support?), numerous security flaws (is MySQL insecure?), and no active development (has MySQL stopped progressing?).

      I'll tell you reasons to use it over PostgreSQL: better support on Windows, nicer client interface, better documentation, from the project itself as well as from third parties, and a much saner upgrade scheme. I also hear that its replication support is much nicer.

      Hey, there are reasons to choose MySQL over PostgreSQL too, especially if you're already familiar with triggers and constraints, if you want to use the inheritable tables, or you're migrating from Oracle. Those are also good reasons.

      It's not 1998 anymore, though. I think people deserve better explanations than "it's teh old b0rked!"

      • Neither of the options Randal presented would be satisfactory for Slashdot: SQLite is too lite, and PostgreSQL is too slow. We have transactions when we need them (which is seldom), we don't need or want stored procedures. Lack of subselects sucks, but you take the good with the bad. So, whatever.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.