hey geeks: recommendations for easy-for-end-user cms - Madame Woo
hey geeks: recommendations for easy-for-end-user cms|
The problem with PHP isn't that it's interpreted; that's usually fine for the web. The problem is that it's a just plain badly designed language. Among my many complaints: there's no database abstraction layer, its MySql bindings don't let you use bound parameters, and its standard library doesn't have a semblance of a sensible naming scheme. The first two are particularly galling for a language whose main use is talking to databases. Oh, and it's insanely irritating trying to write secure code in PHP, without worrying that some crazy quirk of the language or some goofball config option is going to turn around and screw you.
I've written a lot of PHP, and there's a lot of PHP out there; you can mostly get stuff done, and we're going to be maintaining it for a while so it's not exactly instant grounds for not using something. It's easy to learn, at least, so as long as someone else has gone to all the work of dealing with the language, it's reasonably easy to modify stuff. But I've personally sworn off writing anything new in PHP; there's a lot of languages out there that are just better suited.