On Tue, Oct 8, 2019 at 10:12 PM Mike Schinkel <m...@newclarity.net> wrote:
> 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? > Hi, My middle ground is a vote, regardless of outcome. This RFC is pretty simple, a deprecation + removal in a later patch, there's not much to compromise on the implementation. If people think a deprecation should not be done or if it's not worth it, a vote is the way to show that opinion. Pros and cons have been given and people have different opinions about those. Currently a few people on the mailing list are very vocal up to a point where it becomes obnoxious to read their replies, and others are stating that this RFC shouldn't even go into a vote. If there are enough reasons to not deprecate them, the voting process will show this and the RFC will be rejected. Regards, Lynn van der Berg PS. We need a CoC.
