[wp-trac] [WordPress Trac] #33381: Strategize the updating of minimum PHP version.
WordPress Trac
noreply at wordpress.org
Thu Sep 10 14:38:23 UTC 2015
#33381: Strategize the updating of minimum PHP version.
-------------------------------------------------+-------------------------
Reporter: alexander.rohmann | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: General | Version:
Severity: normal | Resolution: maybelater
Keywords: needs-codex dev-feedback 2nd- | Focuses:
opinion |
-------------------------------------------------+-------------------------
Comment (by alexander.rohmann):
Replying to [comment:51 Ipstenu]:
> That just makes it a bully.
No, that just makes it the enabler of a PHP lethargical nightmare that
starts with hosts.
How is WP a bully if...
1. Time is taken to strategize how to implement this.
2. We're talking about a longterm plan.
3. Hosts aren't immediately affected because major version auto updates
won't be served to PHP 5.2.
4. '''Read all the other ideas posted above.''' (try reading objectively?)
I totally agree with everything @TimothyBlynJacobs has said above as well.
I'll even add that this limitation is crippling to developers. Remember
this? http://stackoverflow.com/research/developer-survey-2015#tech-super
Why do you think outside developers find WordPress the 3rd most dreaded
technology?
We're working with an antiquated toolset. "Bully" isn't the right word to
reciprocate, but I (and as is quite apparent many others) are feeling
quite wronged by this. How does "neglected" fit?
After all this time, I don't think any more excuses can be made and I
simply see this is negligence on the part of WordPress to the community.
There needs to be a plan of action.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/33381#comment:54>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list