Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107048
To: internals@lists.php.net
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>
Message-ID: <a2b7c9e4-ee6d-2f71-808b-938272755e00@lsces.uk>
Date: Fri, 13 Sep 2019 08:41:13 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <77CA024D-3141-4707-8280-81CA78282AFA@newclarity.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-thewebhostserver-MailScanner-Information: Please contact the ISP for more information
X-thewebhostserver-MailScanner-ID: 1i8gCh-00GOqH-D1
X-thewebhostserver-MailScanner: Found to be clean
X-thewebhostserver-MailScanner-SpamCheck: 
X-thewebhostserver-MailScanner-From: lester@lsces.uk
X-AuthUser: lester@lsces.uk
X-Envelope-From: <lester@lsces.uk>
Subject: Re: [PHP-DEV] Changing fundamental language behaviors
From: lester@lsces.uk (Lester Caine)

On 12/09/2019 23:16, Mike Schinkel 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 applications 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 skill to fix the problem. Which means they will have to hire expensive programmers — like me!!! — to fix a problem that from their 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 vote on this list will decide if breaking WordPress end-user's site bothers them or not.

Something which does not help here is the way WordPress enforces 
upgrades that may not be compatible with all elements of the themes that 
the user currently has active. I AM a programmer rather than a web 
designer and am having trouble keeping WordPress sites stable. To that 
end I have decided simply to freeze at PHP7.2 for various reasons but 
WordPress is now complaining that the version of PHP is out of date. One 
just can't win ... some of the WordPress sites themes will not even work 
with PHP7 (or WP5) at all. So we *DO* need an LTS version of PHP that 
will run perfectly functional websites for the next ten years while 
others create the next replacement for the likes of WordPress by moving 
framework functionality inside PHP ... Much of the discussion on new 
features cut across the ways frameworks already handle that 
functionality ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - https://lsces.uk/wiki/Contact
L.S.Caine Electronic Services - https://lsces.uk
Model Engineers Digital Workshop - https://medw.uk
Rainbow Digital Media - https://rainbowdigitalmedia.uk