To get the project I need to finish out done by Thursday of next week I’m looking at some frameworks for PHP though I’m not sure they wouldn’t just slow me down.  Ideally they shouldn’t and right now I’m trying to decide between CakePHP and Symfony.  Both are good but it’s pretty much going to be whichever I can pick up on quickest tomorrow or Sunday night.

After I get back from being away I will still have more to do on the project but I should hopefully be able to put some time into the plugins – at the very least I should be able to do some support.  I hope everything doesn’t go to hell in a handbasket while I’m gone.

PHP Logo

Today is 8/8/8, which is interesting for a few reasons, one of which is that it marks the end of PHP 4. What does this mean? It means yesterday’s release of 4.4.9 is the final release of PHP 4. More information can be gleaned from the mailing list archives, beginning with Derick’s request to drop support:

I am trying to gauge what people feel about dropping support for PHP 4 at the end of this year.

Derick caveated his suggestion with the idea of continuing to publish new releases that address security vulnerabilities. Rasmus didn’t see the point:

I don’t really understand what dropping support means if we will still release security fixes. That’s the mode we have been in for at least a year, so what would change at the end of the year?

He suggested a stronger stance:

I’d be more in favour of a statement that put a final death date on it which means no new releases of any sort. We could still say security-fixes only by the end of the year and then death by 08/08/08 or something like that.

So, here we are. PHP 4 is dead. Long live PHP.

Read More at Chris Shiflett: End of Life for PHP 4