My, my this is a heated topic. I am commenting in part because I do not have a dog in this hunt. I am okay leaving it, I am okay if it is deprecated. There are other things for PHP that I care far more about than this RFC. So...
I am wondering if everyone participating in this discussion would be willing to ask themselves "Is there any middle ground where I can respond in a way that is win-win for everyone involved?" rather than retreating to each other's respective corners and fighting as if to the death? If I did not know better I would think this group was filled with members of the US Congress because of the unwillingness to compromise and seek common ground. For example, would those who oppose this RFC change to support it if this was changed from: > Although the deprecation notice itself will carry no backwards > compatibility changes, this RFC is written with the intent that the > backtick operator would eventually be removed in a later version To this?: The deprecation notice will carry no backwards compatibility changes. In addition this RFC is explicitly not recommending removal of the backtick operator in a later version. To remove it — if ever desired — will require an additional RFC to be passed. Maybe the above resolves the objections against this RFC? Or maybe the above makes it useless in the minds of those who want to get rid of backtick? But this specific FRC does not matter to me The point however, is can we not work to some form of happy medium rather than everyone fighting a zero sum game? -Mike #jmtcw
