Is it time to get rid of bundling PHP 4 runtime in VS.Php?

Until now, we have been including both PHP 5 and PHP 4 runtimes with VS.Php. In an attempt to simplify things, I was wondering if we could get rid of the PHP 4 runtime. Afterall, I think everyone has moved to PHP 5 by now since PHP 4 is no longer supported.

What if I get rid of PHP 4 in the next release of VS.Php 2.7? Any issues with that? Please speak up before I get rid of it.

Happy Easters!

Juan

mdcsoft says:

I've never used PHP 4 with VS.PHP except by accident, and that caused me some grief until I realized what I'd done. My vote would be to remove it.

CtrlAltDl says:

I'm still using PHP 4 on a regular basis. It's too hard to switch several hundred PHP 4 files to 5, so I don't see myself upgrading for quite sometime.

juanc says:

Do you use your own web server or do you rely on the built-in apache server?

CtrlAltDl says:

I use our own server (IIS6.0).

strikernl says:

Definitely get rid of it. PHP4 has been EOL for well over a year now, closing in on a year and a half.

If someone insists on using PHP4 (not exactly a recommended practice), they can still use their own web server setup.

This way the focus can completely be on PHP5 and the upcoming PHP6.

Lugaidster says:

I say that you should get rid of it and leave 2.6 as a legacy version for people that still want php4 support. After all, 2.6 should be good enough.

buckleyc says:

Keep it bundled. Not everyone has moved into the PHP 5 world. In a perfect world everyone would always be on the most recent release of a product, but that's just not the case. There is a client I work with quite often who is still on php4 and mysql 4.x. I would like them to migrate, but before I can ask them to do that, I need to make sure their site will not break. Either that or keep the last version that supports php4 available for those who need it.

nicky says:

I would throw it out, it will have positive effects on the stability of the product and the development speed of new features for it.

PHP is backwords compatible so there's no problem in opening php4 files and running them, only the outcome could differ slightly, but you have to make the step at some point... The Developers of PHP allready made their move by cutting PHP4, so why would anyone else still develop for it....

I think there are more important aspects of this app then PHP4 support. The stability needs imporvement and some minor bugs are causing some hastle, removing PHP4 will make development easier and faster, which will benifit all...

after all you could stil release a version that supports PHP4/PHP5 or only PHP4 at a later time...

David56 says:

Not everyone has moved into the PHP 5 world. In a perfect world everyone would always be on the most recent release of a product, but that's just not the case. There is a client I work with quite often who is still on php4 and mysql 4.x. I would like them to migrate, but before I can ask them to do that