News for hackers. Stuff that matters.
Re:A Crash-Course in PHP Namespaces for WordPress Developers by smacktoward on Monday May 07, 2018 @03:59PM (#17015986)
It's a classic chicken-and-egg problem. WordPress supports ancient versions of PHP because they want to be deployable on as many web hosts as possible, including ones that only provide ancient versions of PHP. And web hosts provide ancient versions of PHP because their customers (lots of which are WordPress users) don't demand they provide more recent ones.

It would be a huge help to the overall PHP ecosystem if WordPress started required PHP 7, as this would cut the knot and give those slow-moving Web hosts a reason to upgrade. But requiring PHP 7 would be a much smaller help to WordPress itself, as there's nothing in PHP 7 that WP really needs to do what it does, and dropping PHP 5 support would mean creating a non-trivial number of people for whom WordPress no longer "just works." (As the article notes, PHP 5.2 users only account for around 4% of the overall PHP audience, but the overall PHP audience is huge and 4% of "huge" still equals "a lot.")

So to a degree, asking WordPress to drop support for PHP 5 is asking them to take one for the team. It would be nice if they would, but I can understand why they wouldn't want to.

Re:A Crash-Course in PHP Namespaces for WordPress Developers by Joeri on Monday May 07, 2018 @04:31PM (#17016243)
Moving to php7 would allow those web hosts to host more customers on the same machine, as php7 is faster with a lower memory footprint. Everyone would be better off, even the cheap web hosts.
Re:A Crash-Course in PHP Namespaces for WordPress Developers by smacktoward on Monday May 07, 2018 @04:48PM (#17016365)
I don't disagree that PHP 7 is much better in this regard than 5 is, and most clueful hosts have picked up on this and made the move.

The problem is that there are a lot of less-than-clueful web hosts out there. And if you're less than clueful, the economic rationale for the upgrade probably looks less compelling to you than the "if it ain't broke, don't fix it" rationale for staying with 5 does. (Not to mention that staying with 5 means you don't have to do anything, and less-than-cluefulness and laziness often hang out together.)

Re:A Crash-Course in PHP Namespaces for WordPress Developers by chiefalchemist on Monday May 07, 2018 @05:57PM (#17016814)
> "It's a classic chicken-and-egg problem. WordPress supports ancient versions of PHP because they want to be deployable on as many web hosts as possible, including ones that only provide ancient versions of PHP."

Is the extra 2% of market share worth it? Anyone reasonable would say "nope." Especially when it's handcuffs speed as well as sec.

So then - perhaps - it's about ego and other nonsense?

Put another way, WP has the power and position to lead, yet it chooses to __not__ act in the best interests of its users, hosting companies, and internet users in general. For what, 2% market share points?