In this second part I would like to talk about a few things Composer could do for you, and the PHP community at large, once it is broadly adopted. [...] How can [shared] interfaces be distributed in each project that uses or implements them? This is where I see Composer helping. Composer supports advanced relationships between packages, so to solve this issue you would need three parts.

The three parts all revolve around a few different packages (for their specific Caching interface example) - psr/cache-interface, psr/cache and the requiring of these into a framework needing the common interface. He talks some about what this sort of structure has to offer: simpler plugin installation, promotion of good standards, promotion of code reuse and a renewed interest in using PHP.

Reinventing the package management wheel is another thing that really should stop. Who am I to say this you ask? It is true, we are building a shiny new wheel as well. Yet I take comfort in the fact that we are trying to build a generic solution which will work for everybody.

As part of the grand finale of php|tek '11, Keith Casey announced the winners of the first annual php|architect Impact Awards. These awards are selected by the subscribers of php|architect magazine. They represent the projects that have had the most impact on the day-to-day lives of PHP developers. php|architect is proud to announce the winners of this year's Impact Awards.

Winners this year included the Frapi (in Up & Coming), MySQL (in Data Management), Xdebug (in Integration/Development) and the Best Overall Product winner - the Zend Framework.

• 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.

I woke up this morning to the news of a $44 billion buy-out offer from Microsoft for Yahoo!. This is being covered from all angles in various tech sites like Slashdot but I think the one angle I haven't seen yet is what does this mean for PHP?

He mentions the work that Microsoft and Zend have done to push PHP support on the OS (check out this email too) and he wonders what the final impact of it all could mean for the language - will things change drastically if Microsoft becomes a major player in the PHP world or would they stay behind the scenes and give the community the support it might need.