Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106356 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 39834 invoked from network); 30 Jul 2019 22:12:40 -0000 Received: from unknown (HELO mail-lj1-f170.google.com) (209.85.208.170) by pb1.pair.com with SMTP; 30 Jul 2019 22:12:40 -0000 Received: by mail-lj1-f170.google.com with SMTP id r9so63216095ljg.5 for ; Tue, 30 Jul 2019 12:37:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QKVQJ6FzZ2tISQW+5aCQaR5l6DqnDZRgdrr+hjs78JQ=; b=mc5Ww9Gq53wRFSj8t/slsBGmQBFGv4xfHPu8+bAtUZaIm+5KwCriBjkB1OeHc92GJg zTfhcm8MrBjx44WxUKYRv6i26/zPsxxIjRMz8LNNIotjjnMk26G0qAbPLOQUGqbb/J2C pNBfm60nBZLPnvGa2GlsBABzKwjPqST8XMnJ65i/NDmylJPCpruJJJvTD9B3KlH1yr4m L19/SaQ83kR7k0p/+B51Xqmo4H4DKJllTYEZvgWJGDpt277kSyAGGHk258K0eqAbI3TQ 0Q7j9Y70J9WfH4zb9yHymdrcSnmHZ72eaMJRnXWRzMKWEPFwZfN/FxVES41vQo1OjQ3h uXsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QKVQJ6FzZ2tISQW+5aCQaR5l6DqnDZRgdrr+hjs78JQ=; b=HPxYw3usHw1Ch+K7nwcmLaL+SIjGKD8+l8G4+kbNM6ycQ8p0Ubh8LXSlhBwbg9BKUu fMzTRkreMHOiTEdzkh46DGeXPFqVSE9DADMkn0Kno1yfk9np/a4EGpDe1V/x1kQ/ATIk jX/Zskp51TOO2Bcx1bbwdUVyj6mQVi7dWFFZYtl56vgcYbe6XTE2LyP3g2vdxgfZvMb9 4CtpcSdjaEcrtCrYB7+SYKhuxhIwKNqsq8OpKMcR7wJC7EFuY84JU8RC7/e9+lAjWwB4 A69dP84HJUtIoe4RuywybaN89KQYY/sU75v14iMY8Elp65UcmlqrLElKOQoExakBKZgX NQLQ== X-Gm-Message-State: APjAAAXUo86mADIYagn/Kg4oVSR8gVVQ2NEbUZQ6BMyT+Z1+yRseEVKm K4UNAFeZ06z8LjQqZajNa2Nx8NrPf0Cxg2No64k= X-Google-Smtp-Source: APXvYqx0rJluDPLL93vF78fuCKawjuIgW+qz9o0fs6WliLTeD3fv33PbDWUPEogxcDrwVqhJAONbJ19Y6tt029vZ/c0= X-Received: by 2002:a2e:9685:: with SMTP id q5mr46731281lji.227.1564515457400; Tue, 30 Jul 2019 12:37:37 -0700 (PDT) MIME-Version: 1.0 References: <9aba78c9-f04d-45b8-6c34-ad1c2472ef76@gmail.com> <75d04139-b944-f204-f988-959fa6f3e305@gmail.com> <8CD3B476-ABF9-4DB7-96D3-217064023854@gmail.com> <98616527-805f-3425-d292-1363be26730d@gmail.com> In-Reply-To: Date: Tue, 30 Jul 2019 21:37:21 +0200 Message-ID: To: Zeev Suraski Cc: Bob Weinand , internals Content-Type: multipart/alternative; boundary="0000000000001583bf058eeb248e" Subject: Re: [PHP-DEV] [RFC] Explicit call-site send-by-ref syntax From: nikita.ppv@gmail.com (Nikita Popov) --0000000000001583bf058eeb248e Content-Type: text/plain; charset="UTF-8" On Tue, Jul 30, 2019 at 9:09 PM Zeev Suraski wrote: > On Tue, Jul 30, 2019 at 9:30 PM Bob Weinand wrote: > > > > Am 30.07.2019 um 17:14 schrieb Zeev Suraski : > > > > > Zeev > > > > Before I answer on point - I'd like to thank you that despite the fact you > clearly disagree with me - you wrote your message in a courteous, > respectful tone. > > And now, on point: > > > > You can either silently ignore somebody or announce it. > > > They're both unacceptable, when the feedback is on point - even if you (the > figurative 'you') completely disagree with it. > > > > You may consider it a courtesy to have it announced so that they don't > > wonder why they are not being replied to. > > > > There's absolutely nothing courtesous about it. Both behaviors - silent > ignorance and announced ignorance - are rude. It's debatable which one is > worse - but they're both unacceptable. > > > > Everyone is free on his own who to listen to and who to ignore. > > > > Not everyone. Not people that are requesting comments on their proposals. > There's a reason we call RFCs RFCs. > > Folks who decide to move on with the challenging and tedious process of > changing the language, MUST be willing to do what it takes. And it > absolutely means defending their proposal, including from folks who may > have issues with them. > > If you're not up for it, do not propose. If you propose, be ready to > discuss it in good faith, including with folks with opposing views who take > their time to write detailed feedback. It doesn't matter if you know > there's no way you will be convinced, or that the other party will be > convinced. That discussion is extremely relevant for everyone else who is > supposed to make up their mind about the proposal. > > It's not up to you alone whether it's acceptable. Maybe it isn't for you. > > You're free to say that. But it's definitely not up to you to threaten, > as > > an individual, with "group@". You are not a "we". > > > > I'm confident that if it ever came to that, I'll have the backing of group@ > , > which is why I wrote what I wrote. Perhaps the statement wasn't properly > wordsmithed, but that's what I meant. > Ignoring on-point feedback - from top contributors, no less - is so much > contrary to the spirit on which this project has been based, that it's a no > brainer no-no. > > > > I'd appreciate if, now and in future, you would respect everyones free > > will in that regard; > > > The free will plays a role in one's decision to move forward or not move > forward witha proposal. If they do - it's absolutely their responsibility > to defend their proposal if & when folks scrutinize it and find issues with > it. That's why we have a long, mandatory discussion period. Opting out is > not an option. > > On a partially related note, I think there might be a more comprehensive > solution to polarization we're all (or at least many of us) are suffering > from in terms of the language's direction, one that may make both camps > happy, without turning every RFC into a contentious fight (and not by > updating our rules, but by changing what we offer). I'll spend some time > thinking about it and propose it when it matures a bit, hopefully next > week. > Zeev, I am putting myself at a disadvantage here. I am not suppressing Stas' voice, only removing my own ability to argue against it, and effectively strengthening its position. Everyone else can still see his arguments and be swayed by them. If they're good arguments and well delivered, they will be. If they aren't -- well, that's hardly my own fault. I read RFC feedback and engage in discussions, because I want to deliver the best proposal I can, which incidentally is also the most likely to be accepted. However, not all forms of feedback are created equal. It is a staple of polite debate that criticism be actionable -- it is not sufficient to register your disapproval, you also need to suggest possible avenues for improvement or alternative approaches that may be pursued. If I have found that a particular source of feedback has, over many years, been consistently and persistently negative and only on rare occasions yielded an actionable insight, I believe it is my prerogative to remove this source from my personal consideration, especially if it has a negative influence on my mental well-being. Regards, Nikita --0000000000001583bf058eeb248e--