In a new post to his site Freek Van der Herten covers how some of the changes that happened in Laravel's v5.5 release would impact the packages Spatie shares, some of the more popular PHP packages with a wide range of functionality.

At Spatie we’ve released a auto-discovery facades functionality, LTS releases and how some new functionality replaces (retires) packages Spatie had already released.

Laravel 5.5 is probably the best release yet. But, in all honesty, I think that of every Laravel release. My recommendation is to get your apps upgraded to this version as soon as possible. The reward is that you can make use of all L5.5’s new features and the latest major versions of our packages.

On the Noupe.com site they've posted an article talking about the WordPress REST API that's been included by default in the project and how it will affect developers on the platform.

With the advent of WordPress 4.4 last year in December, we saw the inclusion of the first half of REST API in the WordPress Core, and the rest of it is expected to be with us in the upcoming major release of WordPress. [...] The community is abuzz with all talks about how important REST API will soon be for WordPress development, and how it is going to change the way developers code and interact with WP.

So, how is REST API going to affect the WordPress users and developers, and what exactly will we be able to accomplish using it?

In the article they talk about the impact that the API will have on the "rise of Javascript" in the WordPress application and the role PHP could play in it all. They also talk about cross-platform integrations the REST API makes possible, the Calypso interface that was recently announced and how it opens up a new world of mobile application possibilities.

Giorgio Sironi has a new post to DZone.com today about some of his experiences with Behat, a behavior-driven development testing tool written in PHP. It uses the Gherkin language syntax to define its tests.

I had the occasion to try out and adopt Behat for a particular need in our projects at Onebip. Here is my recount of the experience from a PHPUnit contributor and invested person.

He starts off with a list of situations where he doesn't think that Behat is a good fit for testing including testing of a single object and acceptance tests where comparing the response from more than one test is needed. He suggests that it's more useful for verifying high level business rules than anything. He talks some about the shift they made to using Behat and some of the benefits they found in its use. He finishes up the post by looking at the technical side and includes a warning about letting the size of the FeatureContext file get too large.

In part two of their look at Composer/Packagist, the Nelm.io blog looks at some of the impact they could have if adopted heavily by the PHP community.

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 a part of this year's php|tek conference, the folks at php|architect once again put together their choices for the "Impact Awards", a special recognition for projects that have really made a mark over the last year in a few different categories.

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.

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.

Tony Bibbs, in the wake of last week's surprise from Microsoft to Yahoo, has posted a few of his thoughts on the matter.

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.