Based on the project size, timeframe, and implementation. I've been using PHP for Web-based projects for years now, and I've seen those arguments crop up against it from various soruces. Mostly, those arguments come from ASP forums, Java forums, advocates of other languages, etc. that have no real foundation on a modern PHP implementation. Sure, PHP didn't have session support in version 3. It was added in 4 and improved greatly through the devel cycle of 4, and now we're at 5.
User security? For what? It's a language... It has the same "security" as C, ASP, or others. It's up to the programmer to build a user management system. Unless you go with a framework, but I tend to develop my own so I know what it can and can't do.
Speed wise, there are a lot of arguments about PHP being a scripted, interpreted language. Sure, but use IonCube or Zend Optimizer and that's taken out of the equation.
I've used PHP to develop projects ranging from a handful of users to handling dedicated Web apps running on clusters handling thousands of users at any given time. Never had a problem with speed, reliability, or security. |
