Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95739
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
To: internals@lists.php.net
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com>
 <b3bd7acf-a525-d921-1b1b-64ccf94b858b@gmail.com>
 <A8.67.32927.27DDBC75@pb1.pair.com>
 <CANUQDCjeH45_2aEq74CCEOY4xc3xJ0o_+yRQ2NVy0K2VdOXFBQ@mail.gmail.com>
 <C9.2F.45301.38D6EC75@pb1.pair.com>
 <CAH-PCH5qHdYen33Q_s7kTKM_8qK71v8Ky6kT4fzuRfAwfX06BQ@mail.gmail.com>
 <A7.D5.18051.896CFC75@pb1.pair.com>
 <CAH-PCH568TPsztkWT553QVQy7jsp1tcqT5w+OT1PoCDt-PbUOg@mail.gmail.com>
 <780c8f3d-bc26-37ff-893d-54be8d438c73@lsces.co.uk>
 <7ecffe19-f7be-7b51-f952-013812851c2c@gmail.com>
 <2b8cf7e9-3c66-5c2f-e962-22ad18992aa9@lsces.co.uk>
 <04613dcc-141e-762c-797b-c1f3e7b9b069@gmail.com>
Message-ID: <bdd01546-ca4f-5524-8960-a90e099aa916@lsces.co.uk>
Date: Wed, 7 Sep 2016 12:58:31 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.2
MIME-Version: 1.0
In-Reply-To: <04613dcc-141e-762c-797b-c1f3e7b9b069@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with
 composer/pickle
From: lester@lsces.co.uk (Lester Caine)

On 07/09/16 12:37, Rowan Collins wrote:
> On 07/09/2016 11:51, Lester Caine wrote:
>> This comes down simply to 'education', and just as we provide migration
>> guides to check deprecated code and help re-write it there needs to be
>> the same sort of guideline - provided by PHP - as to how composer or
>> what ever can be used to replace the previous processes. I've seen
>> several examples of how I could be using it, but none that dovetail in
>> with what I have.
> 
> I guess "we", i.e. PHP, should provide migration guides from ways of
> working which we documented in the first place. So is there a document
> that describes your current way of working, that you are trying to
> migrate from? It's hard to know where to begin when you talk about "a
> style of working".

This is the main problem with PHP today. It is SO flexible that there
are probably a dozen ways to do the same thing and all are correct. I
keep being told my way of working is 'old fashioned', but there is no
single path to modernise code which is still working perfectly well on
PHP7. I would appreciate some critique on what would be the right way to
make a large modular set of code into something that conforms better
with a current style of working. I still use multiple files as entry
points stored in folders for each package as that move many years ago
made adding or tailoring functionality an lot easy operation which the
'centralised' code it was developed from made impossible. Namespace
should simply dovetail in to this format, but like other new features
that is not proving advantageous. I'm currently reworking a package for
a new application and can develop it using tools already built into the
framework without needing to change style.

If I was advising a newcomer today what is the best way of starting,
just WHERE would one direct them? Many example are still using mysql and
PHP4 style layouts. What is a good example of a modern PHP application?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk