Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111596 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 33611 invoked from network); 17 Aug 2020 22:24:14 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 17 Aug 2020 22:24:14 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id CDA5418053A for ; Mon, 17 Aug 2020 14:25:13 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from smtp.simply.com (smtp.simply.com [94.231.106.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 17 Aug 2020 14:25:12 -0700 (PDT) Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by smtp.simply.com (Simply.com) with ESMTPSA id 4BVnBb1HMfz62hY for ; Mon, 17 Aug 2020 23:25:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=givoni.dk; s=unoeuro; t=1597699511; bh=vernv05jHSU/Ip/q7COL78AElpCPZHQLk4DxzfDAXL8=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=dtloft1m7n29U/D0xW0h16UWXvYmujHjodruypUN4b2/h2jR0GxxcoPtZ6IfFmWsH yMStvDdTHVP7QbmFOKEC3PGnn857Jc9Wf1QtcffLozbCANhWssEuc0Fiw6NbEG964h iQbYPaWkBtc8oNZAjdliNv4Gwkp22gPUaprT2XpE= Received: by mail-wr1-f51.google.com with SMTP id z18so16306052wrm.12 for ; Mon, 17 Aug 2020 14:25:11 -0700 (PDT) X-Gm-Message-State: AOAM531o6f59xE7OpQVCY2PMS1fo27KH+494NFv9IhufCLMsCCPhRBwX sYFQ4uzWu6CFfEBzugOOnq7Wo2FVjNBXyDCrez8= X-Google-Smtp-Source: ABdhPJylP7W29rriPpTc6fT44O+QMjNL/KHnP7FMkW0CO3m/l6kUjaVClft/a5O3eQarhGDAtkvl9HsS2UnI3LQrLkI= X-Received: by 2002:adf:818b:: with SMTP id 11mr16149840wra.141.1597699510766; Mon, 17 Aug 2020 14:25:10 -0700 (PDT) MIME-Version: 1.0 References: <5cc837df-ab47-628a-d29b-46d7933be973@gmx.net> <3A7CECC3-CDEE-4852-BF4B-4EC7CA1BD538@pmjones.io> <7d6c42a4-53cd-5e38-4ffc-02fe490d66a3@gmx.net> In-Reply-To: Date: Mon, 17 Aug 2020 23:24:59 +0200 X-Gmail-Original-Message-ID: Message-ID: To: Benjamin Eberlei Cc: Benjamin Morel , =?UTF-8?B?TWljaGFlbCBWb8WZw63FoWVrIC0gxIxWVVQgRkVM?= , PHP Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [VOTE] Shorter Attribute Syntax Change From: jakob@givoni.dk (Jakob Givoni) On Sun, Aug 16, 2020 at 11:32 AM Benjamin Eberlei wrote: > > On Sun, Aug 16, 2020 at 10:39 AM Jakob Givoni wrote: >> >> Hi Benjamin, >> >> I'm sorry, but I don't understand your argument. >> It's true that annotations used to be enclosed in a docblock, but that >> is not an argument for saying that attributes NEEDS to be enclosed in >> a block too. >> It's also true that attributes can be followed by many different >> things, but still it doesn't follow that block enclosing is NECESSARY. >> What I'm saying is that there is still no good argument for why >> attribute block syntax is better than non-block syntax. >> The only argument that was presented in the original RFC was not >> convincing, and I pointed out why. > > Nobody says it's ultimately **necessarry** as @@ can work. Thanks for the clarification. This is the first time I've heard someone from the block-delimiter camp concede that @@ is not necessarily objectively "terrible" (as you yourself put it almost a month ago), as it was made out to be. The question is now if it's reasonable at all to change something for 99% purely subjective reasons (no other substantial fact has been put forward other than the VIM argument) well past feature freeze (yes I know it's not a feature, but it's still controversial), even past the beta3 date. And still without respect for letting the discussion phase run its course before putting to a vote. May I remind everybody of a few words long ago from our release manager Sara: > I'm fine with this or any syntax, but FF is 13 days away, you're going to > have to give me something more substantial than "It maybe breaks something > somewhere somehow". > Regards the vote; I don't believe that @@ has been proven unworkable, > however if I'm wrong about that, then the second choice selection from the > last vote would obviously take precedence. > If that's the case, then the solution still seems obvious: Defer attributes > to 8.1. I know a LOT of people will not be happy about that, but it's the most > responsible thing to do if the threat of forking up is that present and > that dangerous. How did we end up here? What started with "[...] a deep sense of unease that we collectively made the wrong decision [...]" may have taken a turn for the worse when it comes to confidence in the process and the community. Or is it just me being dramatic? :-D All the best, Jakob