In article <BF********************@nasal.pacific.net.au>, Bob wrote:
why is perl referred to as a CGI script and not php,
Well, I perfer perl for programming in, I actually think it's more fun
and overall easier. tis also 5 X easier to shoot yourself in the foot
with perl. (But then, in PHP, certain security mistakes seem easier to
make, such as when talking to databases)
php has the facility to execute backticked execute commands that enable the
programmer to use operating system facilities as well ?
I believe PHP was actually _written_ in perl at first.
why would you bother with perl when you can use PHP which is far easier than
that other bloody language.
I wouldn't say PHP is any easier, but PHP is generally faster on the web
side. (unless you're using mod_perl) Perl is generally best on the back
side, (cron processes, etc..) PHP is nice because it has all kinds of
features specifically for web programming. Wouldn't normally use if for
a shell script though, that'd be kind of silly.
For you, I'd definately stick with PHP, since you obviously perfer it.
You might use perl if mod_perl is available and you really need the
added performance or low-level control. (Persistant variables that span
across web requests, not sessions..) mod_perl.. now.. THAT is
hard. :-)
You might use perl if PHP isn't available.
For heavy serious web stuff, I'd recommend Servlets/JSP. (But only if
you can run 1+ web servers, since JSP is not a very standard ISP
package, it's good for applications that might span several machines.)
For things that really need performance, I'd go with C++ (or even
C/assembly) But not if time-to-market is a concern.
For things that are pretty much limited to commands, go with shell or
REXX.
All depends on the requirements and what you like to work in. Why would
an artist use those foul smelling oil paints when they could use
watercolor?
Jamie
--
http://www.geniegate.com Custom web programming
User Management Solutions Perl / PHP / Java / UNIX