in reply to When choosing perl/cgi

First I should note that I have no actual benchmarks to back any of this up

That said, I don't think you're going to find an appreciable performance difference between using C, php, or perl for your CGI programming. Usually, when any of these do not perform with great efficiency, it's because it's not properly optimized, not because it's not the "right" choice. I like to use perl CGI for all my web programming, but that's because I'm also responsible for writing the back ends that my pages will interface with, and using perl for all of it means I only have to

use CGI::Pretty; use MyBackEndInterfaceModule qw( :client );
and off I go, never having to write the interface into the front end; the backend provides a simple API, including functions or methods to interface with it. This also means I can change from a pipe based interface with the backend, to sockets, to shared memory without having to make any changes in the front end. Which will be appreciated if somebody else is writing the user interface, and you haven't done benchmarks to decide which way is fastest yet. For me, it's the ease of implementing this sort of flexibility that makes perl my first choice.

--4c6966653a205468652073656172636820666f
  7220746861742070657266656374204765656b
  20436869632c20746865206f6e652077697468
  2074686520737061726b6c696e672065796573
  2077686f20706c617973206973207261696e2e

Replies are listed 'Best First'.
RE: RE: When choosing perl/cgi
by toadi (Chaplain) on Apr 25, 2000 at 17:54 UTC
    Well,
    I write both; user an backend. This is why I always used a serverside scripting language.
    I have to make websites that are dynamically builded, with a database. Just connect to the database get the entry and display it.
    Found it easy to write 1 page to display all the products + their specifications.

    But nontheless I love perl!!