Some nice things about fastcgi/speedycgi (http://daemoninc.com/speedycgi/)
*) suexec works with it (I consider this huge)
*) don't have to worry about running multiple web servers (one for
   images/static and one for dynamic).
*) one process can't pollute another's.
*) can make changes to .pm's and they are seen as soon as
   you "touch" the main file. (for speedy, I believe fcgi works
   a little different).
*) bad code doesn't take away the httpd's ability to serve files.
*) can probably be hacked to use internet domain sockets as
   opposed to unix domain so that we can run the cgi's on
   a different box. (fastcgi already does this, speedy does not)
*) the architecture just *feels* better to me than having a perl
   interpreter inside the webserver (but my mind is still open).
*) fastcgi is language independant (speedy is not)