Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95014
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.52 as permitted sender)
MIME-Version: 1.0
Reply-To: bishop@php.net
Sender: bishop.bettini@gmail.com
In-Reply-To: <CAEU6NAcjrh9vV7EpP19x-fK-Ocg7zO1DK-X10wbwsFMRRHA49A@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>
Date: Wed, 10 Aug 2016 13:04:46 -0400
Message-ID: <CAEYWF=55JN+yVn83WuFR-8S_Um7-yL1NxiCWeTNTgA_NQOYXWA@mail.gmail.com>
To: Peter Lind <peter.e.lind@gmail.com>
Cc: Lester Caine <lester@lsces.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113dd08a533c900539baa732
Subject: Re: [PHP-DEV] Function auto-loading
From: bishop@php.net (Bishop Bettini)

--001a113dd08a533c900539baa732
Content-Type: text/plain; charset=UTF-8

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.

--001a113dd08a533c900539baa732--