On Thu, Jul 19, 2001 at 09:33:57PM -0500, Philip Guenther wrote:
Coming from a perl programmer, his second paragraph is almost
hilarious. I don't recall Simon ever complaining about all of
perl's single letter commands and flags ($foo = s/foo/bar/eiox).
Not to mention...
[andrew(_at_)ember andrew]$ procmail -v
procmail v3.15 2000/08/25
[andrew(_at_)ember andrew]$ ls -lh /usr/local/bin/procmail
-rwxr-xr-x 1 root other 82k Nov 27 2000 /usr/local/bin/procmail*
[andrew(_at_)ember andrew]$ perl --version
This is perl, v5.6.1 built for sun4-solaris
[andrew(_at_)ember andrew]$ ls -lh /usr/local/bin/perl
-rwxr-xr-x 3 root other 956k Jun 10 14:34 /usr/local/bin/perl*
The size of the perl binary all by itself, let alone Mail::Audit on top of
that is over 10 times that of procmail. There's a reason why mod_perl was
developed for web servers, and it has nothing to do with perl's alternatives
being "old" or "moldy". On even a moderatly loaded mail server, the overhead
of loading the perl binary, and then the Mail::Audit module, for every message
would bring it to it's knees.
On my system procmail is already the LDA, so there's no additional overhead
generated loading the binary to parse and act on my filtering rules.
(Did he really have to call procmail "moldy"? <Sigh> Or maybe that's
a good thing: despite procmail being so 'old' that it's moldy, no one
has come up with a replacement that's as robust and efficient, so it
keeps on ticking...)
It's the M$ argument: "Unix is 30+ years old. You should switch to something
new and 'innovative', that isn't bogged down with all that legacy stuff
(please ignore dos kernel behind the curtain)"
--
Every man should know how to make at least one drink from a foreign country,
preferably one taught to him by a local female with whom he has had a
complicated, unresolved, and quite possibly dangerous dalliance.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail