8
hervet is right about standard adoption. PHP 5 should be the standard used in XOOPS and not php 4. This places XOOPS behind all other frameworks and cms's.
If you read the developers blogs over at PHP, they are considering; for php 6; dropping all deprecated and dead code prior to php 3.
Also supporting this logic, most hosting providers already have php 5 on their servers. Although some might allow you to run the older version using .php4
It's good to see XOOPS adopting new technology that makes for richer web 2.0 sites such as jquery, but php is still the cornerstone of all that is xoops.
I understand that some sites use older XOOPS versions. The logic that they won't update if this current XOOPS doesn't support their modules/server setup is also flawed. All sites eventually need to be updated due to the nature of the web. Even huge sites such as BBC or Amazon get revamped evey now and then. They do this to keep users visiting their sites. This is especially important for corporate sites. Of course the more time you wait to update a site, the more work you will have. This is a consequence. So we shouldn't use this argument as a block from keeping XOOPS from going full php 5.
Another point is one hervet has already stated. XOOPS versions aren't released that often, as such, if we leave full php 5 for the next version, XOOPS modules won't see xoops/php5 features for another +/- 2 years: 1 year for the next version and another year before modules come out fully supporting php5 from xoops. This would place us even more behind other cms's.
