Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107033
MIME-Version: 1.0
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> <CANS-=pexJhtBS=me8RDvg0+BjXWVqmONU4CDVyrGgcsia40YGA@mail.gmail.com>
 <CAJvSBVOm4FHAdr24vra5DrFJqqXXqh1g=c02RdgodWYPZDqd5Q@mail.gmail.com>
 <CANS-=pd9nMcTpNrcJMHKLv-W74KJqWQRmh55iZ-nKoS59iQSUw@mail.gmail.com> <77CA024D-3141-4707-8280-81CA78282AFA@newclarity.net>
In-Reply-To: <77CA024D-3141-4707-8280-81CA78282AFA@newclarity.net>
Date: Fri, 13 Sep 2019 01:21:04 +0200
Message-ID: <CAOwTYAtN=P2rh5SQ46zrcB=Pd96-1nU_JcXXS-BxzpCt61eK-A@mail.gmail.com>
To: Mike Schinkel <mike@newclarity.net>
Cc: Lynn <kjarli@gmail.com>, Peter Bowyer <phpmailinglists@gmail.com>, 
	PHP Internals List <internals@lists.php.net>, Jordi Boggiano <j.boggiano@seld.be>
Content-Type: multipart/alternative; boundary="000000000000ef06be0592636414"
Subject: Re: [PHP-DEV] Changing fundamental language behaviors
From: krakjoe@gmail.com (Joe Watkins)

--000000000000ef06be0592636414
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Zeev,

I'm going to keep this really short and simple ...

You don't have the authority to make unilateral decisions for PHP,.

Nothing you are saying is going to have any effect, the people who actually
work on the language will merge whatever is voted in.

Cheers

On Fri, 13 Sep 2019, 00:17 Mike Schinkel, <mike@newclarity.net> wrote:

> > How many of those are actually developers? Because the way I understand
> this numbers, "powering the web", that doesn't mean 34% are also
> developers. It wouldn't surprise me if a big portion of these application=
s
> could've also be a system written in another language, deployed, plugins
> installed, added some themes and done, no PHP knowledge required.
>
> Most WordPress users are *not* programmers.
>
> Which is why introducing breaking changes to PHP will potentially affect
> them so negatively; because they have no programmers on staff nor any ski=
ll
> to fix the problem. Which means they will have to hire expensive
> programmers =E2=80=94 like me!!! =E2=80=94 to fix a problem that from the=
ir perspective
> they do not understand nor will even recognize a benefit when the code is
> "fixed."
>
> Again, I am just presenting this perspective on this list.  Those who vot=
e
> on this list will decide if breaking WordPress end-user's site bothers th=
em
> or not.
>
>
> -Mike
>
> P.S. I am writing during a break at a WordPress conference, ironically.
>
>

--000000000000ef06be0592636414--