On Sep 12, 2019, at 11:06 AM, Olumide Samson <oludons...@gmail.com> wrote: > I think they could switch to using null instead, or perhaps get something > else to differentiate what they have initialized or not,
Perhaps, but switching the code requires finding the right people to do the work and then funding the changes. A lot of WordPress code marginally maintained is at best — especially WordPress sites. That differs from what it sounds like are the practices of those who are arguing for enforced strictness here on this list. > that shouldn't stop them from using PHP, probably it will only make them not > upgrade to PHP if they think their bad coding practice is the way forward and > the best way to code.. Hopefully my words did not imply that. I think I instead stated that they would likely never upgrade. > This is merely assumptions and you can't speak for companies you don't know, > what's the statistics backing these your use of "ever and never"? It is absolutely an assumption. Based on my experience. But YMMV. That said, I can give you stats for how many WordPress plugins there are on the WordPress repository, around 68,000. And in my experience a sizable percentage of them would break with these changes. Whether or not the PHP community cares about breaking a large number of WordPress sites or not is up to those of you who get to vote. I just commented to include this perspective since I have not seen anyone else mention WordPress on the list recently. > It's up to them, PHP 7 is still available and will always be available for > them to use... Yes. But of course, at some point PHP 7 will no longer be officially supported. At which point PHP7 users will be forced to decide between support and choosing a support direction for their future. And again, #jmtcw -Mike
