in reply to Perl as bloatware

I agree with you. IO::Socket::INET is a base part of the perl distribution, yet none of the core Net:: modules or LWP use it. Why not? Does this point to a problem with the IO::Socket modules? Or do the big-name perl module writers not trust each other?

Also, I must disagee with merlyn (but just a little). IMHO, HTTP is a minimally session oriented protocol. The sessions are just very short and thrown away quickly. To quote a Network Management Philosopher I once knew : "HTTP is the most connectionless protocol to use a connection-oriented transport that I've ever seen"

Replies are listed 'Best First'.
RE: Re: Perl as bloatware
by merlyn (Sage) on Oct 09, 2000 at 18:47 UTC
    Well, that's usually because there's a certain vocal member of the Perl community who kept yelling about how "inefficient" the IO::Socket library was, and so anyone that wants to talk to a socket tends to handwrite the first 10% of object-oriented library and live with their own code.

    Actually, that's amusing, since Graham Barr wrote both IO::Socket and Net::FTP. The fact that he didn't use his own module should tell you something.

    Ease of use does not translate to performance, necessarily.

    -- Randal L. Schwartz, Perl hacker

[reply]

In Section Seekers of Perl Wisdom