I never liked the perl version because of the fact I don't know enough perl to code any hacks. I was about ready to switch to vbulletin, even bought a license, then scream announced the php port. I know php. Picked up on it back when it was in its infancy and love it. Much more can be accomplished with php with less effort than with perl. One suggestion since you are going to devote all the time to php is to modularize the code. This will make it easy to upgrade to each version if you put in the ability to add hacks as modules. You upgrade the core and any new features you add you add them as plugins. Once you have a stable base, which of course would mean a complete rewrite, you add any new features as modules. If there is a bug fix release all you would have to do is code an upgrade script which would update the core files. Nobody would have to waste many hours re-adding hacks because the hacks would be in seperate files. And when you add new features you wouldn't have to touch the core of the software. In the beginning it would be a lot of work, but, in the end it would be much easier to incorporate new features and much easier for users that hack there fourm to upgrade.
The decision to only support the php version is making me think that I might stay arround for a while and see what shakes out. I like w3t and would like to trust Infopop, but, right now I just don't know what to do.
