On the PseudoCoder blog Matt has a new post - "PHP is a spork, Not a City Destroying Monster":

Here's an FJM style breakdown of Carl McDade's well thought out and persuasive article ("PHP is a skill, not a profession"). Haha...no really it's just flamebait crap.

Matt makes light of a lot of the things said in the Hiveminds article, including Carl's comments about the importance of PHP and how it compares to Carl's language of choice, ASP.NET.

With the final decision on the namespace operator announced, several of the PHP community have voiced opinions, comments and concerns about the selection including:

More comments from Lukas Smith
• Thoughts from Danne Lundqvist
• Notes of disagreement from Michael Kimsal
• Comments from Paul Jones
• A push to move on from Johannes Schluter
• Ninh's comments (from a Ruby/Rails fan)
• PHP::Impact's post on the controversy
• Comments from Fredrik Holmstrom
• Jani Hartikainen looks at the choice of "" over "::"
• A post on the PHP::Impact blog
• Some of Michael Kimsal's thoughts on the choice

You can find out more about how this final implementation will be used in this entry on the PHP.net wiki.

On the PHP::Impact blog there's a recent post that details a statistic Paul Jones found with the Zend Framework's performance - a drop in the response time of the front controller between the 1.0 and 1.5 releases.

The most important factor in making a Web application fast is its basic design. You must also know what kinds of processing your framework is doing, and what its bottlenecks are. The best way to find the performance bottlenecks is to monitor the performance counters and to have a thorough understanding of the framework your application is using.

Federico runs some benchmarks of his own (using the Apache benchmarking tool, ab) both with a default "base app" and with a more optimized "take out what you don't need" version.

Lorna Mitchell has posted the last part of her development process towards creating a sample REST server in PHP:

This is part 3 of my article about writing a restful service server. If you haven't already, you might like to read part 1 (covering the core library and grabbing the information we need from the incoming request) and part 2 (covering the service handler itself) before reading this section. This part covers the Response object that I used to return the data to the user in the correct format.

She show how she created the object to push the response back out to the client with an output() method that displays the XML response in a manually generated format.

Since there was such a good response to his previous framework benchmarking post, Paul Jones has come up with a fresh batch of statistics for the latest versions of several frameworks including the Zend Framework, Solar and CakePHP.

By popular request, here is an update of my web framework benchmarks report. [...] In the interest of putting to rest any accusations of bias or favoritism, the entire project codebase is available for public review and criticism here.

Follows the same methods as before, creating "hello world" controllers in each and running the stats against them with the Apache ab tool. A baseline non-framework example is created and tests are run against different versions (including release candidates) of each framework.

I won't spoil the results - you'll just need to check out his post to see who ranked where.

With the recent release of the first alpha of PHP 5.3, the community has been talking and testing this new version - here's just a few:

• Johannes Schluter looking at the actual release
• The PHP 10.0 blog mentioning the impact this new release will have on the language and the web
• and a few tests that Lars Strojny has already run on the release.
• Evert Pot's look at some of the upcoming features of PHP 5.3 (including code)
• Some testing from PHP Freaks
• A note about some testing with the Stubbles framework

You can check out this page on the PHP.net wiki for more information on what's left for the final release and a tentative schedule for the releases in between.

In an effort to keep things a bit more secure (after finding out about this) the symfony team has officially released their own security policy to help prevent issues like that in the future.

You may be wondering why it has been taking us such a long time to react. Here's the main reason: we had not a very strong security alert reporting and qualifying process. This has been fixed recently. So as of now, if you find a security bug in symfony, please send an email to security at symfony-project.com, with as much details as you can and ideally a patch if you can provide one.

The wiki has a whole section on how to report security issues to get them to the right place.

In a response to these comments made by Paul Jones concerning the Prado framework, Mike Naberezny shares his thoughts on the framework, the "PHP way", and how the majority of site functionality out there can really be divided up pretty simply.

He summarizes the functionality in three different methods of handling: "page/file based", "action based", and "component based". He also notes that the interesting fact is that the "page/file based" method seems to be so dominant in the PHP world, only emphasizing the fact that PHP is more of a "get it done" language than anything.

As is pointed out both by Cal Evans and the Zend Developer Zone, there's been another article posted due to the response from the (now infamous) CIO article - "PHP's Enterprise Strengths and Weaknesses, Take 2" (by Zend's John Coggeshall).

So, in the digital toolbox of the developer, where has PHP been designed to work best? And where is it, perhaps, not the best tool for the job? [...] While other languages can surely be used to solve The Web Problem, in this article I explain why PHP is the premier solution for server-side Web scripting.

John talks about how PHP was written for the web, how it approaches and handles web requests, the security of the language and some of the major software packages that are being used in PHP development today (like the Zend Framework, PHPUnit and PECL extensions).

There's been a few posts about the upcoming namespace support in PHP from different bloggers in the community including:

• A post on the Stubbes blog by Frank Kleine and his discoveries of how the "use" keyword needs to be used in your applications
• A follow-up post from Frank as well correcting some of the problems in his first examples
• Some opinions from Richard Heyes on how useful they seem to him
• Brian Moon's comments on the level of traffic that the namespace discussion has been getting on the php.internals mailing list.

Right now there's so many ideas flying around about what namespaces should be and how they should be implemented that it'll be interesting to see which ideas finally come out on top.