There are a number of factors to consider here. One is the kind of web applications you are developing. For simple things (like a web form submission) plain cgi works fine, is quick and easy to do. More complex interactivity will require embeded code in HTML, databases, etc. Another angle to consider is how much existing code is there that you can leverage in your projects. There are tradeoffs to consider between flexibility and simplicity. Most of the time, increasing flexiblity means increasing complexity: the trick is to find the right balance for your situation. There are Perl modules that will allow you to embed code in your web pages. There is tons of code for PHP, Python and Perl available. You might visit the main web sites for these languages and have a look at tutorials, sample code, existing applications. Perhaps in light of your technical background and potential projects one will seem more appropriate.
Ernest Johanson Web Systems Administrator Fuller Theological Seminary On Thu, 7 Dec 2000, D-Man wrote: > Date: Thu, 7 Dec 2000 23:34:14 -0500 > From: D-Man <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: debian-user@lists.debian.org > Subject: Re: OT: Perl or PHP > > I would recommend not using Perl. Perl can let you do lots of complex text > manipulation really easily, but it is a nightmare to debug, let alone > maintain. > It does too much magic with a lack of data types and automagic variables. I > would recommend Python if you want to do CGI scripting. But as someone else > said, you might want PHP instead of CGI scripting. > > -D > > On Tue, 05 Dec 2000 04:27:02 [EMAIL PROTECTED] wrote: > | hi. sorry for the off-topic post. i'm embarking on a journey to be a web > | developer and would like to know if i should use mod.perl or mod.php for > cgi? > | i've searched and read alot of faqs and so far they're all just howtos. > the > | only conclusion i can come up with is with php u can use it directly with > | html > | (plus also call it from html code) whereas with perl the only way u can use > | it > | is to call it from your html code. > | > | am i right with that assumption? > | > | >
