Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95023
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEYWF=55JN+yVn83WuFR-8S_Um7-yL1NxiCWeTNTgA_NQOYXWA@mail.gmail.com>
References: <CADqTB_gBFM_2yNDQemPs68Fab4Hbd8pGj38a3-HSQ+CRcnDyvA@mail.gmail.com>
 <ee6521f3-123b-83bf-5b7f-b20d0bc4b832@lsces.co.uk> <CADqTB_jTGGx=Xvq8vQab2YZoOuuyr7E6a_NWmgaYbARAJPSJ3g@mail.gmail.com>
 <9ccdcfcd-7a1c-42df-c893-398781e1f1d2@lsces.co.uk> <CAESVnVoCkp+ZszmigzmNt6+HLqi8pLB2Xi8a4cYM-=01x=rZqw@mail.gmail.com>
 <e0ff392d-a343-1d14-3fc9-5e42e25b5c50@lsces.co.uk> <CAEU6NAcjrh9vV7EpP19x-fK-Ocg7zO1DK-X10wbwsFMRRHA49A@mail.gmail.com>
 <CAEYWF=55JN+yVn83WuFR-8S_Um7-yL1NxiCWeTNTgA_NQOYXWA@mail.gmail.com>
Date: Wed, 10 Aug 2016 21:36:35 +0200
Message-ID: <CAEU6NAcMhBUq4JFD70+K5uMqvX--j-qc12zHLDOqkgjMAbAH2A@mail.gmail.com>
To: Bishop Bettini <bishop@php.net>
Cc: PHP internals <internals@lists.php.net>, Lester Caine <lester@lsces.co.uk>
Content-Type: multipart/alternative; boundary=001a1146fd9e8b638c0539bcc42f
Subject: Re: [PHP-DEV] Function auto-loading
From: peter.e.lind@gmail.com (Peter Lind)

--001a1146fd9e8b638c0539bcc42f
Content-Type: text/plain; charset=UTF-8

On 10 Aug 2016 19:05, "Bishop Bettini" <bishop@php.net> wrote:
>
> On Wed, Aug 10, 2016 at 5:37 AM, Peter Lind <peter.e.lind@gmail.com>
wrote:
>>
>> On 10 August 2016 at 10:51, Lester Caine <lester@lsces.co.uk> wrote:
>>
>> > On 09/08/16 06:54, Sara Golemon wrote:
>> > > On Mon, Aug 8, 2016 at 9:59 PM, Lester Caine <lester@lsces.co.uk>
wrote:
>> > >> So Composer IS now the rule rather than some optional extra?
>> > >>
>> > > Yes, the community has decided that for us.  Or at least, Composer is
>> > > a *significant* player in the ecosystem of PHP development.
>> > > require_once() might be fine for NiH applications, but for the
>> > > collaborative world of modern PHP, it's the defacto standard.
>> >
>> > Much as PSR also does.
>> > This is probably fine if one is starting a project from scratch, but
>> > with now 15+ years worth of code that does not follow this 'modern
>> > style' it's another barrier to moving code forward. There is nothing
>> > wrong with the code other than newer users done approve of the style of
>> > working :(
>> >
>> >
>> EVERYTHING is a barrier to moving your code forward. You tell the mailing
>> this on a regular basis.
>> Perhaps you should just migrate your 15+ year old code already and be
done
>> with it?
>>
>> Either that or fork PHP and never upgrade again. If you're this unhappy
>> with any/all changes to PHP, that seems a viable option.
>
>
> Please, let's keep the list clean of ad hominem reactions. Lester has a
valid opinion, based on what seems to be a successful legacy of working
code. That kind of code is essential PHP, and I, for one, value his
perspective and welcome his feedback. If we break his code, or establish
barriers to his code modernization efforts, we're probably doing the same
to a whole class of users whom we might not hear from otherwise.

That was not an ad hominem attack. It was a description of the emails
Lester send to the list.

"Update your code or fork PHP" is not a particularly constructive comment.
Neither, of course, is "don't make changes to my programming language of
choice". Especially given that the feature discussed here would not
actually directly influence Lester - he does not have to use it. In
essence, Lester was arguing against this feature because others in the
community would use it, and that would be a problem for him.

From what i can tell, Lester has an infrastructure problem. Not a PHP
problem. But he still wants to halt language development so the community
doesn't pick up new features that might make problems in his code. That
does not seem reasonable to me.

--001a1146fd9e8b638c0539bcc42f--