Something I really don't like about cfm and php is how the scripts don't stay in memory, which sort of forces you to break it up into smaller scripts that can load and execute quickly. I would much rather just have all the code for a particular site in one script that stays in memory, and whenever I want it to do something, I just call it.
You can create subroutines or functions which can reside in a single file or files that you simply include or require in your scripts that can be used over and over again. Is that something you have looked into yet?
Mod_perl is easy to work with. There is a simple mode where most normal CGI scripts are pulled into memory and "just work". And there are more advanced modes of integration that are less CGI-like and more and more plugging code directly into the web server.
[infoworld.com...]
ok, but then does it "bog down the server"?
Perl by itself does not "bog down the server". It's up to programmer to make sure that it does not happen.
Perl has very good garbage collection (GC) system.
compiled languages so sound really nice to me though...I was thinking of picking up JSP
Perl will keep compiled version of the script in memory. So we really are comparing apples to apples.
I just find it really annoying to work with most of these web scripting langs. I wish they were more like regular services.
What you consider "regular services" might not be the same for others. For me Perl is pretty regular, every day life.