Re: Changing fundamental language behaviors

On Thu, Sep 12, 2019 at 3:06 PM Olumide Samson <oludonsexy@gmail.com> wrote: > On Thu, Sep 12, 2019 at 8:00 PM Michael Babker <michael.babker@gmail.com> > wrote: > > > On Thu, Sep 12, 2019 at 1:51 PM Peter Kokot <peterkokot@gmail.com> > wrote: > > > > > Just a dumb idea, since there clearly is a majority in favor of the > > > change with these warnings and strictness and all that now... Why not > > > making something like an LTS PHP 7.x where all the legacy code would > > > work OK as long as practically possible and 8.x+ would be the future > > > of what the developers want and not what business wants? One who won't > > > upgrade due to the BC breaks also won't need the new features anyway > > > very realistically. > > > > > > > Please don't tie the notion of LTS with the idea that a new major can > break > > BC at will or create larger scale breaks because the previous major has > > extended support. Sooner or later that will end up back at the ++ idea > and > > fragmentation encouraged by the language is a bad idea. > > > > Not sure you are really seeing the goal... > > Why is LTS not a good idea? > And, if the majority want this or that, can we just blow everything into > full dictatorship where i can host my fork of PHP doing uncountable > unwanted things i can call it..? > > Any which way, i think the majority of us are tired of writing bad codes, > but since the language is allowing it we don't have choices than to spend > some hours or weeks later debugging the wrong or right line we did that > last "big mistake", who knows there might be another line smiling coz i > haven't detected it... > I can write good code without sacrificing the flexibility provided by PHP. Don't force ME to write code a specific way because you aren't disciplined enough to not write bad code without the compiler forcing you to do things a certain way. Of all of the justifications for this RFC I've heard, "I can't stop writing bad code as long as I'm allowed to" has to be the worst. -- Chase Peeler chasepeeler@gmail.com