WordPress 3.2 has two changes that may affect some users: the minimum PHP and MySQL versions required will be PHP 5.2.4 and MySQL 5.0. That means PHP 4 will no longer be supported by WordPress itself.
As a plugin developer, PHP 4 definitely makes life more complicated. Plugins end up becoming bloated when you need to have separate code for both PHP 4 and PHP 5. Removing the dependency on PHP 4 allows WordPress to remove old code and help streamline the entire codebase.
What does that mean for the users of our products?
Both WPtouch Pro and Piggy currently work with later versions of PHP 4 currently. Some time after WordPress 3.2 comes out, we will deprecate support for PHP 4.
Internally our policy has always been to try (when possible) to support the last two major versions, so when 3.2 comes out we’ll be supporting it and 3.1. But as development proceeds on the next version of WordPress, we’ll remove the PHP 4 aspects from our code and start using PHP 5 exclusively. That allows the code to be smaller, newer (usually more efficient) and we can use PHP 5 functions only, which in general results in a faster development cycle.
WordTwit Pro, which has just been released requires PHP 5 already.
So if you’re a WordPress user you should start looking at what your host provides in PHP support to make sure you’re ready when 3.2 is released. On many hosts switching to PHP 5 is as simple as clicking a button in the hosting control panel, and on others you can usually add a small snippet to your .htaccess file. Unfortunately there are still some hosts that do not provide PHP 5 at all, and for those you will probably have to find an alternate host, or explain to them why they should add support immediately to allow their customers to upgrade their WordPress installations.