Marco Tabini (of php|architect magazine) has posted some of his thoughts on why PHP just might be the "new Java" in the upcoming year.

Historically, PHP has been developed following the scratch-an-itch method [...]. This development process makes for some haphazard functionality, and has, in the past, been the source of many annoyances that need to be handled with extreme care.

He does mention some of the good things that have come out of this process like OOP in PHP4, SimpleXML functionality and type hinting but warns that if things swing too much the other way (planning out everything, only adding things by committee) that PHP might swerve towards a dangerous precedent - the Java community's mentality.

Marco Tabini (of php|architect magazine) has posted some of his thoughts on why PHP just might be the "new Java" in the upcoming year.

Historically, PHP has been developed following the scratch-an-itch method [...]. This development process makes for some haphazard functionality, and has, in the past, been the source of many annoyances that need to be handled with extreme care.

He does mention some of the good things that have come out of this process like OOP in PHP4, SimpleXML functionality and type hinting but warns that if things swing too much the other way (planning out everything, only adding things by committee) that PHP might swerve towards a dangerous precedent - the Java community's mentality.

On the PHP-Tools blog, there's a noteStubbles.

Stubbles is a new framework for PHP 5.2 which focuses on clean OO design, the use of patterns and ports some features from the langauges commonly referred to "enterprise languages" to PHP. If you are looking for new ways to develop your PHP applications, you should definitely take a look at the stubReflection package, which brings Java Annotations to PHP. The next issue of the German PHP Magazin will feature an article, that shows how to use this package.

The blog has been set up to give the community a window into the framework abd will include things like tutorials, thoughts on the framework and its direction, and maybe a little general PHP talk to balance things out. Check out the framework and the blog at stubbles.org.

On the PHP-Tools blog, there's a noteStubbles.

Stubbles is a new framework for PHP 5.2 which focuses on clean OO design, the use of patterns and ports some features from the langauges commonly referred to "enterprise languages" to PHP. If you are looking for new ways to develop your PHP applications, you should definitely take a look at the stubReflection package, which brings Java Annotations to PHP. The next issue of the German PHP Magazin will feature an article, that shows how to use this package.

The blog has been set up to give the community a window into the framework abd will include things like tutorials, thoughts on the framework and its direction, and maybe a little general PHP talk to balance things out. Check out the framework and the blog at stubbles.org.

Sometimes developers just don't think about how much trouble they'd cause with a rewrite of existing software. They think that moving up to the latest and greatest is the way to go, and that it makes perfect sense to say out with the old and in with the new. Aaron Wormus disagrees. Well, sometimes - it depends on the circumstances, really.

At ZendCon I talked about "Planning a PHP 4 to PHP 5 codebase rewrite, a practical approach". The talk was based on my own experience, as well as famous discussion of the topic such as Joel Spolsky's "Things you should never do" and the examination of "famous" platform rewrites.

Aaron gives an example of a large company making a move from a COBOL system out to C for a mission critical system. Based on his tale, they didn't put the thought needed into making this move - new development time, keeping old developers on staff, etc - besides the fact that customers don't like change and making a move to another platform is almost definitely going to be noticed by them.

Sometimes developers just don't think about how much trouble they'd cause with a rewrite of existing software. They think that moving up to the latest and greatest is the way to go, and that it makes perfect sense to say out with the old and in with the new. Aaron Wormus disagrees. Well, sometimes - it depends on the circumstances, really.

At ZendCon I talked about "Planning a PHP 4 to PHP 5 codebase rewrite, a practical approach". The talk was based on my own experience, as well as famous discussion of the topic such as Joel Spolsky's "Things you should never do" and the examination of "famous" platform rewrites.

Aaron gives an example of a large company making a move from a COBOL system out to C for a mission critical system. Based on his tale, they didn't put the thought needed into making this move - new development time, keeping old developers on staff, etc - besides the fact that customers don't like change and making a move to another platform is almost definitely going to be noticed by them.