Comments on: You Used PHP to Write WHAT?! http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/ web, money and etc. Sun, 06 Jul 2008 05:50:14 +0000 http://wordpress.org/?v=2.5.1 By: PHP Encoder http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5924 PHP Encoder Wed, 02 Apr 2008 18:03:13 +0000 http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5924 You can use PHP for shell scripting no problem. However I do agree that this is not effective language for this. You can use PHP for shell scripting no problem. However I do agree that this is not effective language for this.

]]> By: Hartmut Holzgraefe http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5912 Hartmut Holzgraefe Mon, 04 Feb 2008 11:29:57 +0000 http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5912 You don't need to weaken the security of your server at all, PHP when used for scripting is executed using the PHP Command Line Interface binary (CLI) and you can have separate php.ini files for web server and command line use just fine You don’t need to weaken the security of your server at all, PHP when used for scripting is executed using the PHP Command Line Interface binary (CLI) and you can have separate php.ini files for web server and command line use just fine

]]> By: John J. http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5911 John J. Fri, 01 Feb 2008 20:33:43 +0000 http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5911 @sapphirecat: The only valid one of the "do not use" cases I see is the shell scripting, just because there are many better ways of doing it. Also, in many shell scripting cases, you need to weaken the security of your server in general to allow exec, etc. This is mostly only a problem on shared hosting environments where you don't want one user's httpd to affect someone else's site. The rest of it is just FUD and BS. @sapphirecat: The only valid one of the “do not use” cases I see is the shell scripting, just because there are many better ways of doing it. Also, in many shell scripting cases, you need to weaken the security of your server in general to allow exec, etc. This is mostly only a problem on shared hosting environments where you don’t want one user’s httpd to affect someone else’s site.

The rest of it is just FUD and BS.

]]> By: sapphirecat http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5909 sapphirecat Fri, 01 Feb 2008 17:47:30 +0000 http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5909 Umm, are any of their "do not use" concerns even valid? In particular, I find PHP just fine for shell scripting (even if Console_Getopt could stand some serious overhaul). I even wrote a proof-of-concept once for how we could use PHP and Smarty to generate our Apache configuration. (The project wasn't approved by management, but the POC was perfect.) Umm, are any of their “do not use” concerns even valid? In particular, I find PHP just fine for shell scripting (even if Console_Getopt could stand some serious overhaul). I even wrote a proof-of-concept once for how we could use PHP and Smarty to generate our Apache configuration. (The project wasn’t approved by management, but the POC was perfect.)

]]> By: funny http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5908 funny Fri, 01 Feb 2008 17:32:02 +0000 http://livebookmark.net/journal/2008/02/01/you-used-php-to-write-what/#comment-5908 Harhar he completly disqualifies himself with this entry http://kenhess.wordpress.com/2007/09/21/the-i-hate-java-fan-club/ Harhar he completly disqualifies himself with this entry
http://kenhess.wordpress.com/2007/09/21/the-i-hate-java-fan-club/

]]>