

You will also see some nice ways to build services with PHP. PEAR is a collection of userspace code for solving many Web-related problems that didn't belong in the core of the language itself. Namespaces is another feature that is coming.Īt the higher level, I think you can expect PEAR to start becoming much more useful.

But there are some things that can be improved with respect to this OOP support. PHP has traditionally been a procedural language, and OOP features have crept in over the years to the point where PHP can be used as a decent OOP language. Q: What's interesting in the works for near-term PHP future developments?Ī: Deep in the guts of PHP, the object-oriented program is going to be improved a bit.

You also wouldn't write any sort of middle-layer system for a three-tier architecture in PHP.Īs the top presentation layer in a three-tier architecture, PHP does just fine. For example, you would never write a full back-end database engine in PHP. As you move more towards the back end, PHP usefulness starts to decrease. PHP's strength is in the front-end Web interface. Q: What do you see as its drawbacks? What Web tasks do you think it's less well-suited for?Ī: There really aren't any drawbacks when it comes to Web tasks, but I guess that depends a little bit on where you draw the line between Web tasks and back-end tasks associated with the Web. Rasmus Lerdorf, inventor of the PHP scripting language
