upvote
What is their stance on breaking existing code?

I was testing some PHP ~5 code in 8.3 and there was some questionable backwards compatibility decisions. eg methods that previously returned true / false to indicate success now threw errors, same message signature and all.

reply
PHP is EXTREMELY backwards-compatible in general. All breaking changes are (i.e. were up to this point) usually introduced very gradually, first emitting Notices and Warnings and not without a very good reason.
reply
For a certain value of "gradually". Whether it's too fast or not comes down to opinion (and some of the changes themselves come down to a difference of opinion on how a given language feature "should" work), but it's the reason so many old sites are stuck on PHP5 - because it's not fully backwards-compatible.

A poster phrased it well on here recently¹: "in general lots of users being on unsupported releases should also cause some reflection why that is. E.g. maybe support periods are too short or there are too many breaking changes with new releases."

¹ https://news.ycombinator.com/item?id=50194270

reply
> I know that introducing such a behavior by default could break existing code

Specifically because older versions of PHP didn't have "..." arguments - variadic functions used func_get_args() to access their arguments.

reply
Probably possible to just set up PHPStan or Mago to do this statically, no?
reply