Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95616
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.172 as permitted sender)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (1.0)
In-Reply-To: <1ce3511e-5dcf-522a-6cce-edda9ecd7531@lsces.co.uk>
Date: Sun, 4 Sep 2016 20:32:07 +1000
Cc: internals@lists.php.net
Content-Transfer-Encoding: quoted-printable
Message-ID: <2395F5FB-C2C3-4740-8802-B851D01D208B@gmail.com>
References: <CANaX5nf5S6aS-ZaB=51qvXv+wbReGb2petPBDogTA+MNMHyysQ@mail.gmail.com> <b3bd7acf-a525-d921-1b1b-64ccf94b858b@gmail.com> <2e2e7a2d-4459-c59f-6552-b01314a06b2f@lsces.co.uk> <82d74255-4118-46f4-c073-35e3b224fef8@gmail.com> <eed6f3c1-96eb-65ef-815e-4026048aaeca@lsces.co.uk> <f79f5c81-c0e4-cd51-8d91-24f66e4191fa@gmail.com> <1ce3511e-5dcf-522a-6cce-edda9ecd7531@lsces.co.uk>
To: Lester Caine <lester@lsces.co.uk>
Subject: Re: [PHP-DEV] [RFC] Deprecate PEAR/PECL & Replace with composer/pickle
From: davidkmuir@gmail.com (David Muir)


> On 4 Sep 2016, at 6:48 PM, Lester Caine <lester@lsces.co.uk> wrote:
>=20
>> On 03/09/16 22:53, Rowan Collins wrote:
>> I guess we could have a philosophical debate about what it means for
>> something to be "the standard" rather than "a standard", and whether
>> PEAR was "more official" than PHP-FIG, and just who gets to decide what
>> PHP is.
>>=20
>> But once again, I find myself being drawn into an off-topic debate about
>> coding styles, and I would like to apologise to Davey as it has nothing
>> to do with his RFC.
>=20
> I think that what is missing is a discussion on just where one should
> start these days in terms of a basic framework for beginners. That there
> are so many competing "standards" that in many cases do not play well
> together is MY problem. That my key libraries ARE moving to a different
> style and have different ways of loading is a pull one way, and my web
> side interface has other loaders handling javascript and css packages
> which adds to the complexity.
>=20
> But perhaps we don't bother about the novice PHP user and just assume
> they are all simply using third party frameworks already so all that
> needs to be looked at is improving the library/framework developer
> experience. It would be nice to get back to some BASIC functionality
> such as loading a form, validating it's content, and string the results
> without having a dozen ways of filtering the inputs and a dozen ways of
> accessing the database.
>=20
> --=20
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=3Dcontact
> 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
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20


How many competing autoloading standards are there? PSR-0 (PEAR, Zend, etc) a=
nd PSR-4 are the two main ones I know of. Symphony used to have their own st=
yle back in the day, but swapped to PSR-0 with Symfony2 8? years ago. I supp=
ose you could also work with just a class map, which I've seen some libs use=
 (eg TCPDF)... That said if you've got some other style, just register a loa=
der for it and get on with it. Sounds to me like your problem isn't with Com=
poser per se, but autoloading in general?

Cheers,
David=