Re: Re: Re: Re: Really, how do I get input from the keyboard.

Wow. I thought bad-mouthing CGI was apostacy around the Monastery. I'd like to hear more. Anyway, in the original post, I was trying to avoid CGI, HTML, forms, etc., but now know that for my application, it won't work.

—Brad
"A little yeast leavens the whole dough."

Comment on Re: Re: Re: Re: Really, how do I get input from the keyboard.

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Really, how do I get input from the keyboard. by BUU (Prior) on Feb 20, 2004 at 21:43 UTC
In short I think CGI.pm is slow bloated and unintuitive. The bloat comes from trying to support two hundred different options from generating html to parsing uris to header types and stuff ot that nature. It's slow, well, it just is! Look for benchmarks vs cgi::lite/simple. As for unintuitive, this is purely subjective of course, but I vastly prefer the cgi::lite approach where I have one method, parse_form_data, which takes a 'form data type' field and returns a nice simple hash. I can then use this hash however I want. It's simple.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Re: Really, how do I get input from the keyboard.
by BUU (Prior) on Feb 20, 2004 at 21:43 UTC

In short I think CGI.pm is slow bloated and unintuitive. The bloat comes from trying to support two hundred different options from generating html to parsing uris to header types and stuff ot that nature. It's slow, well, it just is! Look for benchmarks vs cgi::lite/simple. As for unintuitive, this is purely subjective of course, but I vastly prefer the cgi::lite approach where I have one method, parse_form_data, which takes a 'form data type' field and returns a nice simple hash. I can then use this hash however I want. It's simple.

[reply]