Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:65283 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67593 invoked from network); 28 Jan 2013 19:01:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jan 2013 19:01:52 -0000 Authentication-Results: pb1.pair.com header.from=linepogl@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=linepogl@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.172 as permitted sender) X-PHP-List-Original-Sender: linepogl@gmail.com X-Host-Fingerprint: 209.85.223.172 mail-ie0-f172.google.com Received: from [209.85.223.172] ([209.85.223.172:57297] helo=mail-ie0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 64/37-28517-F1BC6015 for ; Mon, 28 Jan 2013 14:01:52 -0500 Received: by mail-ie0-f172.google.com with SMTP id c10so1205985ieb.31 for ; Mon, 28 Jan 2013 11:01:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=42RYZaUao2WJd6R4g2Cg/vjdKl918zxtRz/ksDmqIGM=; b=X1xDXfBSvNL+haU6+XTluYI4vTi+RSEPziIp8/iCE5+l9XUBu8a/5ftmgOuw45VgCR AymHej1obJdOLWTLRIq+qdeg9MjN9FxothRf4wJm3yaKR8TJQGsDDJaQ6rkqGPnnAD3J 3o4S6yEXJLJYDWVt30J0ftdyzyQ9mFSNafD9x6hKbwuxed+cQ8SUdR8zo+bl/7/4KfaU CoaksjuiezgpKXtpQ0FA+kup09SGmHkCd/Sze1Ykz2mrVHLl1y3T+XPRCA9c1xXqKoaW pnfD/5nX+XJEWD0l4tJed2UuTkdXMuGgp5yOv5DcqnEJ4hmijRwCVBWsrFXxVEK5O6ns VIWQ== X-Received: by 10.50.53.161 with SMTP id c1mr5566747igp.95.1359399709545; Mon, 28 Jan 2013 11:01:49 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.86.20 with HTTP; Mon, 28 Jan 2013 11:01:27 -0800 (PST) In-Reply-To: References: <76a9565b2a095a72063a68f106a6b457@mail.gmail.com> <5ed6711b24349c82b7c17dd450ff7c80@mail.gmail.com> <7165e8331e1070234771f7ae9573cdf8@mail.gmail.com> <5106690E.6040908@zerocue.com> <510679E0.1050603@zerocue.com> Date: Mon, 28 Jan 2013 20:01:27 +0100 Message-ID: To: Zeev Suraski Cc: Clint Priest , Peter Cowburn , Pierre Joye , PHP internals Content-Type: multipart/alternative; boundary=f46d04339d18cb96f004d45de874 Subject: Re: [PHP-DEV] Voting periods From: linepogl@gmail.com (Lazare Inepologlou) --f46d04339d18cb96f004d45de874 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2013/1/28 Zeev Suraski > > -----Original Message----- > > From: Clint Priest [mailto:cpriest@zerocue.com] > > Sent: Monday, January 28, 2013 3:15 PM > > To: Peter Cowburn > > Cc: Zeev Suraski; Pierre Joye; PHP internals > > Subject: Re: [PHP-DEV] Voting periods > > > > > > On 1/28/2013 6:12 AM, Peter Cowburn wrote: > > > On 28 January 2013 12:03, Clint Priest wrote: > > >> If you're still worried about this making it in, don't worry. Nikita > > >> and I have given up, to the determinant of the community. > > >> > > > Then please close the voting. > > Since there is no "maximum voting period" and 5.5 is not in a feature > freeze yet, > > I left the voting open, in case some people decided to read the patch > and change > > their minds. I see no reason to close the vote unless I'm required to > do so or the > > game is up. > > I think there's an almost-consensus that voting periods need to be well > defined. Two reasons: > > 1. If you care enough about it you should be able to vote about it within > one or two weeks. > 2. Leaving it open ended gives the RFC proposer too much power. He could > simply end the vote once it happens to reach the necessary majority. > > So I'd say yes, you're required to end it, either immediately or at most > at the end of the two week boundary. > > > asking for this feature (present in every other modern > > language) for 5+ years. I spent two years going through the *tedious* > RFC > > discussion process, wrote the software, Nikita made it even better to > have it > > shot down without even reasonable explanations as to why "from most > people." > > There are two very reasonable explanations, and it's fine you may disagre= e > with them: > > 1. It makes the language more complex. > 2. It makes the language more difficult to maintain. > This is not accurate. There are people who would like to see a feature implemented, but voted no because they did not like the proposed implementation. This is important. A blunt "No" blocks not only the RFC itself but also all attempts for alternative or improved solutions. I believe that all proposals should have 3 options: "Yes, all the way", "Yes in principle, but not this implementation" and "No in principle". This would leave room for better approaches. > > In both cases, the people who opposed it thought that the gain from addin= g > it doesn't outweigh these loss in complexity and maintenance overhead. > > > Some are resting on the idea that the ROI isn't there just aren't > listening to the > > community. > > The vast majority of the PHP community is a silent one; These people > don't participate here on internals; They don't attend conferences; The= y > use it - the vast majority of them in a professional manner - and they > picked it because they like it the way it is, not because of what it need= s > to become. For every person that subscribes to internals, there's a > thousand (yes, a THOUSAND) people who don't (it's several thousands vs.~5 > million). In fact, they're not completely silent. They speak in volumes > - PHP 5.4 is used in less than 1% of the sites using PHP today, and even > the relatively revolutionary 5.3 is still a lot less popular than 5.2. > The new shiny features are not all that interesting for most people. > > The community that participates in internals isn't necessarily > representative of the community at large. > > Zeev > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Lazare INEPOLOGLOU Ing=C3=A9nieur Logiciel --f46d04339d18cb96f004d45de874--