On 10 Aug 2016 19:05, "Bishop Bettini" <bis...@php.net> wrote: > > On Wed, Aug 10, 2016 at 5:37 AM, Peter Lind <peter.e.l...@gmail.com> wrote: >> >> On 10 August 2016 at 10:51, Lester Caine <les...@lsces.co.uk> wrote: >> >> > On 09/08/16 06:54, Sara Golemon wrote: >> > > On Mon, Aug 8, 2016 at 9:59 PM, Lester Caine <les...@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.
