Re: Future stability of PHP?

What's meaningful in this sense? I have a budget for supporting open source projects (back to my money v time point) and a percentage of that is for the PHP Foundation. I'd happily pay LTS fees we pay elsewhere (even sometimes as a safety net) to the Foundation but believe that the money we give to projects is just that, a donation that the project can use as it sees fit, rather than the purchasing of a service as we do commercially. Best wishes, Matt > On 11 Apr 2023, at 09:56, Marco Pivetta <ocramius@gmail.com> wrote: > > I'm also curious to hear whether any participants in this thread do/did > support the PHP foundation in any tangible way :D > > If you treat it like an LTS provider, perhaps it's time to pay up the LTS > support fees? > > Marco Pivetta > > https://mastodon.social/@ocramius > > https://ocramius.github.io/ > > > On Tue, 11 Apr 2023 at 10:40, Alex Wells <autaut03@gmail.com> wrote: > >> On Tue, Apr 11, 2023 at 6:10 AM Deleu <deleugyn@gmail.com> wrote: >> >>> I don't want to use those weird stuff, but I'm >>> doing the best I can to replace every single line of old code that has >> been >>> written in an era that "best practices for PHP development" were not what >>> you and I know today. >>> >> >> I still do not understand why you're expecting the whole PHP project to put >> in enormous efforts to keep the backwards compatibility and solve your >> problems (temporarily) instead of you doing so. What's stopping you from >> using the last supported PHP version by that codebase and fixing or, worst >> case scenario, rewriting it if you wish, while on that (non latest) PHP >> version? What causes the desperation to update to the latest PHP? Is it new >> features or security fixes, or both? >>