Focusing on PHP day in and day out is nice, but sometimes it's good to branch out a bit. Kevin Yank agrees and decided to give Python a try. He's written up this post to the SitePoint PHP blog as he explores the language from a PHP developer's perspective.

Like may SitePoint readers, I cut my teeth on PHP. I've become very comfortable with it over the years, warts and all. PHP continues to be a dependable choice, but PHP hasn’t changed a whole lot lately. [...] Python has a lot in common with PHP: it’s a dynamically typed, open source scripting language with excellent documentation and a thriving community around it.

He includes a few basic "Hello World" kinds of examples in Python just to introduce you to the language structure (indenting for code structure? that's crazy talk for us PHPers) and some of the handy features of the language like sequences and the language's automatic namespace support.

In a new post on the IBM developerWorks page, Nathan Good takes a look at some of the features of the up and coming versions of the PHP language including things like namespaces, changes in the XML handling and a few things taken out.

PHP's next edition, V6, includes new features and syntax improvements that will make it easier to use from an object-oriented standpoint. Other important features, such as Unicode support in many of the core functions, mean that PHP V6 is positioned for better international support and robustness.

New features he mentions include namespace support, improvements to the native Unicode support as well as a few of the things that will be permanently retired like the php.ini settings for magic_quotes and register_globals.

The CodeUtopia blog asks the online community for their opinion - what do you think of PHP as a first language?

Sometimes I've seen people say PHP is a bad first language, because it teaches bad programming habits. But is this actually true at all? Often those who say that don't really like PHP themselves either, many times because of equally untrue reasons.

They argue both sides of the situation, mentioning what could make for a good first language, why PHP is a "nearly perfect" fit for it and some arguing points for the other side as to why PHP isn't the best option.

As Matthew Weir O'Phinney points out, David Hansson (of Rails fame) has posted a few comments on what he calls the "immediacy of PHP".

I love the fact that it's all just self-contained. That the language includes so many helpful functions in the box. [...] PHP scales down like no other package for the web and it deserves more credit for tackling that scope.

and to that, Matthew comments:

It's nice to see leaders of projects like Rails having this same attitude. It's a breath of fresh air in the competitive market of web development frameworks.

On the PHP.net website, the official announcement for TestFest 2008 has been posted:

The PHP-QA team would like to announce the TestFest for the month of May 2008. The TestFest is an event that aims at improving the code coverage of the test suite for the PHP language itself. As part of this event, local User Groups (UG) are invited to join the TestFest. These UGs can meet physically or come together virtually. The point however is that people network to learn together.

The event is not only a teamwork/friendship building effort but will also help out the PHP.net mentors in a serious way - testing has largely been their responsibility and having a wealth of user-submitted tests to help out cuts their workload dramatically.

You can find out how to get you and your local PHP user group involved, head over to the TestFest homepage.

Lukas Smith is "pre-announcing" the effort he and several other core PHP developers have put together to try and help the PHP language become that much more solid - TestFest.

I am posting this blog post to get a last round of feedback before we go live with a proper announcement on PHP.net. The current state of the discussion is available for all to read on the newly created PHP.net wiki. Please read through it and provide comments either in this blog, in an email to me or to the php-qa mailinglist.

They're also looking for developers to help with the web interface they'll need (the "simple back-end" that the moderators can use to handle the incoming test submissions). Complete information about the event can be found on its wiki page.

Resulting from a conversation among developers at this year's PHP Quebec 2008 conference, a new event has been created to help test PHP against as many different configurations as it can be - TestFest.

The TestFest is an event that aims at improving the code coverage of the test suite for the PHP language itself. As part of this event local UG are invited to join the TestFest. All it takes is a local organizer to spear head the event and to get others involved in writing phpt tests. The submissions will then be reviewed by members of php.net before getting included in the official test suite.

The even will be announced sometime in March and its hope is to get as many people in the community involved to improve the language. There'll also be a raffle to give away 10 of the stuffed elePHPants as well as, for the ones who are "test worthy" and seem able to write up good tests on their own - commit CVS access to php.net as well as an official php.net account.

For more details on the event, check out this page on the (new) PHP.net wiki.

Piggybacking on a recent proposal for traits in PHP, Lukas Smith has suggested something that could help make the organization of these sorts of contributions (and their "staying power") a bit more likely to happen - an official PHP.net wiki of sorts.

As such I really like what Stefan has done with his Traits proposal. Very nicely done. [...] Right now the RFC documents are hidden away in the unwieldy mailinglist archive and Stefan's private homepage, which could disappear any day. Of course there are also the various web archives, but what would be nice to have is a PHP.net wiki.

He notes that not only would this help protect information like this from dropping off the face of the web but it might also pave the way for some other changes to be made to the language (and to provide a space where everyone can share their ideas). He specifically mentions his wants for an array_merge_replace and a change to file_exists.

As Cal Evans and others in the PHP community have pointed out, there's a post on Tim Bray's blog (of Sun Microsystems) with his prediction for PHP for the upcoming year:

The short version: PHP will remain popular but its growth will slow, as people get nervous about its maintainability and security stories.

He does mention the two different stances of this statement - the good side (with low entry level, good applications and speed) and the stance he seems to believe in more - that there are just things about PHP and how its handled that could cause major issues down the line.

Be sure to check out the comments for community views on both sides of the story too.

On the Stubbles blog, Frank Kleine has pointed out a proposal from Stefan Marr to include functionality for traits in PHP.

As a language construct within PHP it would be very easy to do the same, but easier to learn and to use. Beside some keyword issues (the RFC uses "use" as keyword, but this will of course conflict with namespaces) I'm wondering what this will have an impact on reflection - the RFC stays unclear about this.

A trait is a free-floating chink of functionality that, instead of being confined to a class (or file) that has to be called on to use it, exists where the developer can use it from anywhere at any time. This helps solve some of the issues with single inheritance in PHP.