on Friday, February 1st, 2008
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.