in reply to Re: CGI made me bloated
in thread CGI made me bloated

I'm really not looking for a fight over CGI.pm, I just wanted to hear what other people had to say about it. I also use the module quite extensively when I have to write any scripts for the web, but my point is that I hardly use it for anything but obtaining parameters from html forms.

As well, I was not making the claim that the LWP modules should be used instead of CGI.pm, but the name just sprung to mind when I was thinking of another web-related module to chant rhythmically to myself.

My gripe, then, if I have to have one, is whether there is a need for so much baggage and repetition among modules? It seems that a lot of CGI.pm has fallen by the wayside as newer and more task-specific modules have been developed, so why hold on to all the bloat?

matt

Replies are listed 'Best First'.
(ichimunki) Re x 3: CGI made me bloated
by ichimunki (Priest) on Oct 31, 2001 at 20:10 UTC
    If you are writing web client software, not using LWP would be a major oversight. So yes. Add that to the chanting litany. :)

    I've used CGI for fun and have just started using it for profit just last week. I agree that it would be nice to have a module that was more easily broken down into its functional elements, but given that what we have works I don't see compelling reasons to change it-- at least not quickly.

    On the server, my first guess is that speed is related more to your processor, your RAM, and whether or not you are maintaining your perl script in memory using something like mod_perl, than it is going to be related to whether or not the CGI module itself is "bloated".

    As to whether we are "over loading" by bringing in functionality that we aren't going to use when we "use CGI;", so what? Every time I load perl I load lots of stuff I don't need-- it's an inherent danger in an interpreted language. The resulting executable is a hybrid of the interpreter and my code. And with a language that allows fancy stuff like eval() it gets even worse. Imagine a native C program that compiled and ran variable C code on the fly. (There's your spooky thought for Halloween. *grin* )