You may have heard about the goPHP5 website, which is an organization that wanted to get web hosts and open source projects to phase out PHP4 (what many hosts use by default now) and focus on PHP5. (Since the project started, PHP.net announced that it focus would be on PHP5 at the end of the year, with only security updates to PHP4 after that time.
The change, going from PHP4 to PHP5, was controversial for some. Other, like Drupal, ebraced it. Matt M., WordPress' Benevolent Dictator for Life, didn't like it much.
Now, I'm not a coder, and I couldn't tell you the differences between PHP4 and PHP5, but I know one thing: The internet is ever-changing. If it wasn't, we'd still be using FrontPage -- everyone.... Ewwwwww -- and all our webpages would end in .htm. And even if PHP5 is flawed, it's the only way we'd ever get to PHP6. We all have to adapt.
But Matt's comments were pretty insipid. He said: "Let's make sure we have really solid importers for all the CMSs on that
list.
(And wow that website is ugly.)"
Is that really the thinking that goes into WordPress? It's sure not forward-thinking. (Of course, I don't think WordPress is know for that.) It would seem everyone is comfortable at WPHQ.
And as for goPHP5's website being ugly: yes, it is. But by attacking the style of the site and discussing the substance is pretty lame. And let's not forget Wordpress.org. Talk about bland...
So with PHP5 on its way, I think WordPress developers should start thinking about WordPress 3, the PHP5 version of the blogware. With this release, they could take everything that makes WordPress great, and make it even better. Drop the legacy code (which would annoy some plugin makers and theme designers, but they'll adjust). Keep the user-friendliness of it.
And start thinking about the future instead of living in the past.
Other links:
- Projects going with PHP5
- Hosts going with PHP5
- Matt M's comments on PHP5
- funkatron: What Matt Mullenweg doesn’t know about PHP5, and how it hurts him and his users

