2006 May
Wednesday, May 3rd, 2006
at 4:00pm
I just saw this post over on PHPDeveloper.org, which refers to this scary-sounding bug relating to $_POST array behavior in PHP 5.1.3.
If you haven't upgraded yet (as I have not), it might make sense to wait this out a day or two to see what happens next. Thanks to all those who caught this and reported it.
Monday, May 1st, 2006
at 5:26pm
I usually hear about this sort of thing through an announcment list or one of the PHP feeds I follow, but instead I was just pleaseantly surprised to visit the home page of php.net this evening and learn that PHP 5.1.3 is out.
Some particularly nice-looking benefits in this release include the removal of deprecation warnings for the 'var' keyword in class properties under E_STRICT, and the overhauled FastCGI interface. Of course, the most important benefits are the collection of stability refinements and bug fixes.
Timing is perfect from my perspective on the FastCGI overhaul, as I'm looking forward to really digging into the lighttpd/PHP 5 FastCGI combination this month. I know this topic has come up before a number of times, and many people have made the switch ... so, I'm planning to give it a whirl as well. I would be very interested to hear from anyone who's already made the switch to hear if the FastCGI rewrite in PHP 5.1.3 makes a noticable performance difference.
Monday, May 1st, 2006
at 3:43am
As I mentioned in February, I've had a blog and site overhaul underway for awhile. Like a lot of developers, I always find it hard to take the time to work on my own site.
With the aid of the excellent Matt Brett, I've got a new theme in place for this site. I can't thank Matt enough -- he's been a pleasure to work with, and I highly recommend him.
I've scrambled a bit this evening to get this in place as part of the May 1 CSS Reboot event. Not sure if I'll have time to crank out the new Pearified.com design by the evening of May 1, but I'll do what I can. If I can't get to it, I'll certainly roll it out before the end of the week.
Please let me know if you find any issues or errors with the new site -- any that you find are my fault, not Matt's.