I figured I could ask that.
I've often met situations where I wanted to turn silly create_function() calls into closures, but this morning -- more frustration for me. I figured I could rewrite the cache handler to basically link cache_get_data and cache_put_data together by putting the regeneration code into a closure, which would then allow me to easily benchmark regeneration times, instead of just cache storage times.
So, this just means-- "I'd really like to use PHP 5.3 in Wedge."
But then, it also means that a third of all servers won't be able to install Wedge. IIRC, Wedge.org runs on PHP 5.5 or something, and my Wampserver has PHP 5.3, so it's not a problem for me, and generally speaking I think that the '5.2 third' portion is likely to be a portion of servers that have either been abandoned, or just not maintained very often, and thus more likely to cause configuration problems when using Wedge.
In short:
- 5.2 is the current version required by Wedge. PHP 5.2 is great.
- 5.3 is a bit better, not THAT much better, but I've been wanting to do closures for years, just like I'm doing in JavaScript. Going for PHP 5.3 won't make my life much easier, and won't make Wedge better. But still, I'd like to look into it.
The competition usually has a required PHP version < 5.3: xenForo has 5.2 IIRC, SMF has something like 4.0 (lulz, but they're trying to account for website upgrades, while I'm betting on website importing), even newer software like esoTalk only requires 'PHP 5'. Vanilla, I think has a requirement of 5.1. The only 'popular' PHP package I know of that requires PHP 5.3 is Laravel, and it's a framework, not a forum package. So, both logic and statistics tell me to keep using 5.2, although maybe, well... Maybe it's okay, hence this poll.
Remember, Wedge is striving to remain compatible with as many browsers as possible; but when it comes to the server behind it, this is usually something that most serious webmasters CAN control, and personally, I like being in charge!
I've often met situations where I wanted to turn silly create_function() calls into closures, but this morning -- more frustration for me. I figured I could rewrite the cache handler to basically link cache_get_data and cache_put_data together by putting the regeneration code into a closure, which would then allow me to easily benchmark regeneration times, instead of just cache storage times.
So, this just means-- "I'd really like to use PHP 5.3 in Wedge."
But then, it also means that a third of all servers won't be able to install Wedge. IIRC, Wedge.org runs on PHP 5.5 or something, and my Wampserver has PHP 5.3, so it's not a problem for me, and generally speaking I think that the '5.2 third' portion is likely to be a portion of servers that have either been abandoned, or just not maintained very often, and thus more likely to cause configuration problems when using Wedge.
In short:
- 5.2 is the current version required by Wedge. PHP 5.2 is great.
- 5.3 is a bit better, not THAT much better, but I've been wanting to do closures for years, just like I'm doing in JavaScript. Going for PHP 5.3 won't make my life much easier, and won't make Wedge better. But still, I'd like to look into it.
The competition usually has a required PHP version < 5.3: xenForo has 5.2 IIRC, SMF has something like 4.0 (lulz, but they're trying to account for website upgrades, while I'm betting on website importing), even newer software like esoTalk only requires 'PHP 5'. Vanilla, I think has a requirement of 5.1. The only 'popular' PHP package I know of that requires PHP 5.3 is Laravel, and it's a framework, not a forum package. So, both logic and statistics tell me to keep using 5.2, although maybe, well... Maybe it's okay, hence this poll.
Remember, Wedge is striving to remain compatible with as many browsers as possible; but when it comes to the server behind it, this is usually something that most serious webmasters CAN control, and personally, I like being in charge!