On 24-6-2026 16:24, Tim Düsterhus wrote:
... <snip>....
Tim, I've asked you before to not try to gaslight me, but your current mail still does. Your current mail also seems to be largely a response to things I didn't write, so I have no idea what you are trying to do here, other than just sprouting rhetoric which everyone has heard before and nobody is (currently) arguing about.
I just offered to help improve the information available regarding the proposals without an opinion about the individual proposals and without voicing an opinion on the principle of deprecations (and for the record: I have no problem with the principle).
I have no interest in arguing with you about things which I didn't bring up and which aren't relevant to what I offered.
If the justification for a deprecation is strong enough, no impact analysis will be able to stop the deprecation from happening. The only thing the impact analysis can do in that case, is mentally prepare people for the amount of work ahead and inform the decision whether the eventual removal of the feature should be in PHP 9.0, or should be delayed to PHP 10.0.
Being against adding an impact analysis for fear of this influencing the vote, is kind of how Brexit happened, which really truly isn't the "golden standard" you seem to think it is....
My offer to help create an impact analysis for the majority of the current deprecation proposals still stands. Anyone who wants to take me up on that, is welcome to ping me.
Smile, Juliette
