3 ms·

Just don’t upgrade to PHP 8 then? All of those decisions were made for specific reasons. I’ve noticed anyone complaining about PHP 8 for legacy reasons was bar

• JonathanBeuys 3y ago
  You can't let web software sit on a stack that does not get security updates. The last release of PHP 5 was less than 5 years ago. Javascript from 20 years ago still works fine. That's the way it should be.
  • gog 3y ago
    If you are upgrading your web software stack, why aren't you upgrading your web software?
  • withinboredom 3y ago
    There are services you can pay for that backport security fixes to old versions of php.
  • danogentili 3y ago
    Javascript is a client-side language, you don't have control of the software stack, thus (ideally, if you want to) you have to write code to support every version, even a prehistoric chrome build from 2015 (be it directly or indirectly via transpiling and polyfills). PHP is not like that, like in every other language where you can control the entire environment, it evolves and things break, and that's the way it should be, that's why we have semantic versioning.