Re: PHP vs Perl for system scripts (non-web)

From: Date: Tue, 28 Jan 2003 00:52:35 +0000
Subject: Re: PHP vs Perl for system scripts (non-web)
References: 1  Groups: php.general 
Request: Send a blank email to php-general+get-133330@lists.php.net to get a copy of this message
If you like php better, i'd stick with it; however, for almost all of my un-web-related stuff, i use perl. i'm pretty sure they would run at about the same speeds/efficency. "Paul Chvostek" <paul+php@it.ca> wrote in message news:20030127190921.A25117@mail.it.ca... > > I have to write a swath of code to manage system-related stuff based on > database content. Scripts will be run as root by cron, and determine > what they have to do via user interaction and SQL lookups. Functions > will include manipulation of system configuration files, legacy text > file configs, and some signalling with posix_kill. On some of the > machines in question, there won't even be an httpd installed, so I'd be > building a php as a standalone binary, and running it with shell magic > and a -q option. I've done this kind of stuff in the past in smaller > environments, and it seems to work nicely. > > I'm more comfortable writing stuff in PHP. I use PHP alot more, and I > find the resultant code more readable and easier to maintain. Aside > from Perl's ubiquity and the dubious advantage of future flexibility by > using Perl's DBI interface to talk to different SQL servers (I'm using > MySQL at the moment), are there any compelling reasons I should write > system stuff in Perl rather than PHP? > > Thanks. > > -- > Paul Chvostek <paul@it.ca> > Operations / Abuse / Whatever > it.canada, hosting and development ŒåPP4Ñáqû > o]8http://www.it.ca/ >

« previous php.general (#133330) next »