In this post on the Zend Developer Zone, Cal Evans takes a look at an article published in a recent php|architect issue from Chris Hartjes about how several recent advancements in the PHP community have helped developers think more in "the Rails way" of development.

Chris does a good job of laying out his points. As with any article of this nature, you are going to agree with some of them and you’ll disagree with some of them. However, to get to that point you’ll have to consider all of them. That’s really the point of the article; making developer sit back and think for a minute. It’s well worth the read.

Cal also mentions some of the topics presented in the article including more conceptual ideas like "Convention Over Configuration" and "Rapid Should Mean Rapid".

In this post on the Zend Developer Zone, Cal Evans takes a look at an article published in a recent php|architect issue from Chris Hartjes about how several recent advancements in the PHP community have helped developers think more in "the Rails way" of development.

Chris does a good job of laying out his points. As with any article of this nature, you are going to agree with some of them and you’ll disagree with some of them. However, to get to that point you’ll have to consider all of them. That’s really the point of the article; making developer sit back and think for a minute. It’s well worth the read.

Cal also mentions some of the topics presented in the article including more conceptual ideas like "Convention Over Configuration" and "Rapid Should Mean Rapid".

Continuing on with his look at events in PHP, Alexander Netkachev takes another look today at another type of approach to his handy feature - the "Java way".

In my previous article I summarized event system definitions and showed an example of PHP event model, which is built with the call_user_func() function. This acticle expands the subject by introducing an advanced PHP event model that is based on sender/eventObject/listener collaboration, which was popularized by the Java world.

He steps through some examples with ProtocolCommandSupport.java and ProtocolCommandListener.java functionality, showing how to take that functionality back over to PHP and implement it using the built-in features.

Continuing on with his look at events in PHP, Alexander Netkachev takes another look today at another type of approach to his handy feature - the "Java way".

In my previous article I summarized event system definitions and showed an example of PHP event model, which is built with the call_user_func() function. This acticle expands the subject by introducing an advanced PHP event model that is based on sender/eventObject/listener collaboration, which was popularized by the Java world.

He steps through some examples with ProtocolCommandSupport.java and ProtocolCommandListener.java functionality, showing how to take that functionality back over to PHP and implement it using the built-in features.

In a new post on his blog today, Paul Jones mentions a framework that might bridge the gap for ASP developers making the move over to PHP, Prado, and some of the issues that more traditional PHP developers might see around it.

He talks about how the framework is structured and what non-PHPers might find to like about it, but he also wonders if the phrase "the PHP way" might be better replaced by a more definitive term to describe the way most PHP develoers prefer their apps to work.

In a new post on his blog today, Paul Jones mentions a framework that might bridge the gap for ASP developers making the move over to PHP, Prado, and some of the issues that more traditional PHP developers might see around it.

He talks about how the framework is structured and what non-PHPers might find to like about it, but he also wonders if the phrase "the PHP way" might be better replaced by a more definitive term to describe the way most PHP develoers prefer their apps to work.

In conjection with the release of PEAR 1.4.9 as previously mentioned, Greg Beaver wants to clarify some things when it comes to setting up a PEAR channel in "the official way" and with the correct pakcages.

There has been quite a bit of confusion recently due to the best resource for setting up a channel being located on Toby's blog, and now being quite a few versions out of date. First of all, let it be known that the PEAR_Server package located at pear.chiaraquartet.net has been superseded by the Chiara_PEAR_Server package at pear.chiaraquartet.net.

The rest of the post is concerned with his checklist and step-by-step guide to getting and setting up the needed software. It's the whole process, right down to creating a nice frontend for the users and how to test your channel to ensure it's properly set up.

It's definitely the definitive guide to setting up a PEAR channel correctly.

In conjection with the release of PEAR 1.4.9 as previously mentioned, Greg Beaver wants to clarify some things when it comes to setting up a PEAR channel in "the official way" and with the correct pakcages.

There has been quite a bit of confusion recently due to the best resource for setting up a channel being located on Toby's blog, and now being quite a few versions out of date. First of all, let it be known that the PEAR_Server package located at pear.chiaraquartet.net has been superseded by the Chiara_PEAR_Server package at pear.chiaraquartet.net.

The rest of the post is concerned with his checklist and step-by-step guide to getting and setting up the needed software. It's the whole process, right down to creating a nice frontend for the users and how to test your channel to ensure it's properly set up.

It's definitely the definitive guide to setting up a PEAR channel correctly.

From Builder.co.au, there's this new article that talks about the LAMP software, how's it's "showing the way" to Open Source security.

The most popular open-source software is also the most free of bugs, according to the first results of a U.S. government-sponsored effort to help make such software as secure as possible.

The so-called LAMP stack of open-source software has a lower bug density--the number of bugs per thousand lines of code--than a baseline of 32 open-source projects analysed, Coverity, a maker of code analysis tools, announced Monday.

The results are a product of a Homeland Security effort (performed by Stanford University) for three years. They found that the LAMP combination contained about 0.434 bugs per 1,000 lines of code. Unfortunately, their results also showed, of those problems, PHP had the higest bug count of the four.

From Builder.co.au, there's this new article that talks about the LAMP software, how's it's "showing the way" to Open Source security.

The most popular open-source software is also the most free of bugs, according to the first results of a U.S. government-sponsored effort to help make such software as secure as possible.

The so-called LAMP stack of open-source software has a lower bug density--the number of bugs per thousand lines of code--than a baseline of 32 open-source projects analysed, Coverity, a maker of code analysis tools, announced Monday.

The results are a product of a Homeland Security effort (performed by Stanford University) for three years. They found that the LAMP combination contained about 0.434 bugs per 1,000 lines of code. Unfortunately, their results also showed, of those problems, PHP had the higest bug count of the four.