Re^7: Should I just print my own HTTP headers?

But what if you've already tuned the important things?

Then you'd be wasting your time to optimize it further. Optimizing for developer efficiency is just as important (if not more) than optimizing for CPU time!

We're talking about a script that probably won't exceed 30 lines so it's not exactly difficult to maintain.

Ah, the optimism of youth. Trust me, if it's at all useful it will grow. Even if it doesn't grow, someone (maybe you) will copy and paste your nasty hack into a much larger program.

Yes, but it is useful in that it tells you how to optimize what you've already decided to optimize. I'd love to write it in C, but 1) I don't know C.

You should learn C. Then you'll realize that you don't want to write it (or anything) in C unless you absolutely have to. A 30 line Perl program is likely to be 300+ lines of C! The crack about C was meant to be ironic!

-sam

Comment on Re^7: Should I just print my own HTTP headers?

Replies are listed 'Best First'.
Re^8: Should I just print my own HTTP headers? by Cap'n Steve (Friar) on Apr 11, 2007 at 21:16 UTC
How is "print $header;" less maintainable than "$cgi->header($header);"? If it grows, then I've designed the whole site wrong. If it turns out I've designed the whole site wrong, it probably won't kill me to rewrite a dozen lines to use CGI.	[reply]
Re^9: Should I just print my own HTTP headers? by samtregar (Abbot) on Apr 12, 2007 at 01:46 UTC
I don't remember saying anything about maintainability. I thought we were talking about your pointless desire to optimize away CGI.pm... -sam	[reply]