Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107024
Message-ID: <26337F23-F0D8-4774-964A-0BFE682041F3@newclarity.net>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A6CE569A-D830-421A-97BA-29AB16D501BD"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 12 Sep 2019 14:46:02 -0700
In-Reply-To: <CAAwbVufSPH=YjZZO5y4gzROS1e-ok+rpYrrBvGO-=DOnvtCKSw@mail.gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
To: Olumide Samson <oludonsexy@gmail.com>
References: <076701d56978$86020910$92061b30$@php.net>
 <CADyq6sK4HektgfDpCCFR3=bumyPaf9vn=-WdvaboHybBQKd53g@mail.gmail.com>
 <078e01d5697c$5512bc10$ff383430$@php.net>
 <CAKws9z1EBSqCFy2wD3cEV49KDSJOd6tT04PrCkxG8+3Hb6WpTA@mail.gmail.com>
 <CAPKYkKw1EU3Qp6W7b19r4kMKPD1HntH+7NQSxSiDNcLXqPERMA@mail.gmail.com>
 <CAKuGYLRWF9jnS-Zs+uRFNN1pgRSvHFpW-FChgNq9Rk282AFFGA@mail.gmail.com>
 <CAPKYkKxUyeWWZY5OyDLtAYiDUYLkwyMjuc_Wq2Y++3C9CP6G1w@mail.gmail.com>
 <CANS-=pc7Av0+jSKNebb-iae+BpTt6_72kRSHSowb-hon4rxUgQ@mail.gmail.com>
 <31BD63BC-ACE0-4478-B241-E698D2D6F59C@newclarity.net>
 <CAAwbVufSPH=YjZZO5y4gzROS1e-ok+rpYrrBvGO-=DOnvtCKSw@mail.gmail.com>
Subject: Re: [PHP-DEV] Changing fundamental language behaviors
From: mike@newclarity.net (Mike Schinkel)

--Apple-Mail=_A6CE569A-D830-421A-97BA-29AB16D501BD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Sep 12, 2019, at 11:06 AM, Olumide Samson <oludonsexy@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 =E2=80=94 =
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. =20

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...=20

Yes. But of course, at some point PHP 7 will no longer be officially =
supported. =20

At which point PHP7 users will be forced to decide between support and =
choosing a support direction for their future.

And again, #jmtcw

-Mike


--Apple-Mail=_A6CE569A-D830-421A-97BA-29AB16D501BD--