in reply to Re^5: Should I just print my own HTTP headers?
in thread Should I just print my own HTTP headers?

Question: Why continue to advocate the use of a module that carries the weight of all that extraneous functionality, when it seems that everybody who has any expertise in perl/cgi applications adamantly decries the use of so much of it in favour of templating? Especially when there is a drop-in, cut-down replacement derived from it, that does away with that weight?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."
  • Comment on Re^6: Should I just print my own HTTP headers?

Replies are listed 'Best First'.
Re^7: Should I just print my own HTTP headers?
by chromatic (Archbishop) on Apr 09, 2007 at 23:21 UTC

    I prefer CGI::Simple as well, but if the choice is between using a core module and writing bizarre and meaningless benchmarks to "prove" that the core module is Just Too Heavy to use, I'll take the core module.

[reply]
      bizarre and meaningless benchmarks

      Which benchmark is that?

      Update. There are two posts in this thread that could be called benchmarks. I just wondered which one you meant.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

In Section Seekers of Perl Wisdom