You Used PHP to Write WHAT?!
by Harun Yayli on Friday, February 1st, 2008 at 9:03 am under Industry, PHP, Technology, WTF
There is an article on PHP on CIO, bashing it a bit.
PHP may be the most popular Web scripting language in the world. But despite a large collection of nails, not every tool is a hammer. So when should it be used, and when would another dynamic programming language be a better choice? We identify its strengths and weaknesses.
For the ones, who doesn’t know about CIO, their target audience is managerial. not developers.
So potentially reader will be your manager and they’ll get this info as a reference.
I’m copy/pasting some parts of it for your convenience. Let’s assume your manager does not know about PHP (I hope not) and you’re about to convince him/her to use PHP on a project. What whould he/she think after reading this?
When should you use PHP?
- Creating an intranet site.
- Prototyping an application that will be converted to Java or some other language.
- Creating a Web database application.
- Deploying an inexpensive or quick solution.
- Using ready-made apps from Sourceforge.net or other sites.
In general you should not use PHP:
- Where data security is of high importance.
- In Shell or automated scripted applications.
- In enterprise applications where scalability takes higher precedence than economy.
What a short sight!?!? Kenneth Hess the author of the article, is also the new “On The Desktop” columnist for Linux Magazine. Honestly, I would not really expect these claims from Ken Hess.
Please share your comment.
Link: You Used PHP to Write WHAT?!
Recent Entries
- new pecl/memcache is out with memcache.php
- memcache.php flushes servers
- memcache.php can delete keys now
- memcache.php is now part of pecl/memcache
- memcache.php goes PECL
- memcache.php stats like apc.php
- oci_bind_by_name maxlength is not so optional
- Is Sun going to buy PHP too?(PHP Quebec 2008)
- PHP APC apc_shm_create error on CLI
- Facebook’s Buggy Spam Detection
Harhar he completly disqualifies himself with this entry
February 1st, 2008 at 12:32 pmhttp://kenhess.wordpress.com/2007/09/21/the-i-hate-java-fan-club/
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.)
February 1st, 2008 at 12:47 pm@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.
February 1st, 2008 at 3:33 pmYou 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
February 4th, 2008 at 6:29 amYou can use PHP for shell scripting no problem. However I do agree that this is not effective language for this.
April 2nd, 2008 at 1:03 pm