Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60127 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33777 invoked from network); 17 Apr 2012 23:00:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Apr 2012 23:00:31 -0000 Authentication-Results: pb1.pair.com smtp.mail=kris.craig@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kris.craig@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.42 as permitted sender) X-PHP-List-Original-Sender: kris.craig@gmail.com X-Host-Fingerprint: 74.125.82.42 mail-wg0-f42.google.com Received: from [74.125.82.42] ([74.125.82.42:49176] helo=mail-wg0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F4/B9-21594-E06FD8F4 for ; Tue, 17 Apr 2012 19:00:30 -0400 Received: by wgbds11 with SMTP id ds11so83638wgb.5 for ; Tue, 17 Apr 2012 16:00:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=v8/ME3AvlA7c+X8QllBaNtCGBdxVHpnt5QrDQ9J9DYc=; b=DZnR8yPtPTBhJGNQjDshO/kj7RliKAE8201ILhcASMDeN+DDp51rXuYnYCueZV0nSd ++ZmMfMFE6vUyXfGkDHGlow6NVAMxNs15T79V70C5pi3IINsJlEWIqUvRk8jTEUbKS0z 4hfvgvFehqVWIl8zvL6QiWTjsgMkoSHJ91OGs00AmeZ6iYz/T6vF5bhg3IFgO8TA0K8H gONpGGwZeRiZPTF7wUFCV788VzloR1JVptvEk1saA01cgz/j6uftCLanFvxzlkuFL27r oFKWexOI7ey+CAkgEbbcqvWl5JvAM8jJK2xvjCZb/4bIU007NzyOmIEip37lqLbjiN75 99qA== MIME-Version: 1.0 Received: by 10.180.91.168 with SMTP id cf8mr677834wib.0.1334703627595; Tue, 17 Apr 2012 16:00:27 -0700 (PDT) Received: by 10.223.1.82 with HTTP; Tue, 17 Apr 2012 16:00:27 -0700 (PDT) In-Reply-To: <8CE43BBE-F338-43F3-A75A-99B80E7F2648@seancoates.com> References: <4F8D1469.9030709@lerdorf.com> <4F8DC894.50804@lerdorf.com> <8CE43BBE-F338-43F3-A75A-99B80E7F2648@seancoates.com> Date: Tue, 17 Apr 2012 16:00:27 -0700 Message-ID: To: Sean Coates Cc: PHP internals Content-Type: multipart/alternative; boundary=f46d043893479a711f04bde7e769 Subject: Re: [PHP-DEV] Some Stats From: kris.craig@gmail.com (Kris Craig) --f46d043893479a711f04bde7e769 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On Tue, Apr 17, 2012 at 3:42 PM, Sean Coates wrote: > My response earlier was meant to be funny, mostly, but I did also intend > to convey some of the same things Rasmus said. The only person who wants = to > participate in a conversation where someone is hogging the floor is the > person doing the talking. > > Yeah one of the problems that really frustrates the hell out of me is tha= t, > after I've answered a question or responded to an objection, somebody new > jumps in and raises the exact same issue. When I tell them to read earli= er > in the thread for my answer, they tend to get hostile and will often just > keep re-repeating the criticism until I finally get fed-up and just repea= t > the response I'd posted earlier. Rinse and repeat. > > > In my opinion, the main reason this happens is because of your "natural > verbosity" (as you put it). People are busy=97especially smart people. Yo= u > want the smart people to be able to read the important bits of your > proposals/ideas, but most of them are unwilling and unable to sift throug= h > hundreds of messages. This is why they ask questions that have already be= en > answered. > But isn't that just a circular argument? I.e. "They're not reading the list because its too cluttered," and, "They're cluttering the list because they're not reading it." If people would read the first few messages in a thread, there wouldn't be all this clutter because they wouldn't be asking questions that have already been answered. And if they can't be troubled to do that, then they should hold-off on posting. Busy or not, rule #1 on any forum is that you should *read* the thread you're responding to. Yes, I can do my part by making my posts more succinct and I'll work on that, but what I'm saying is it's a two-way street. Me doing that alone won't be enough to solve this problem. Here's my rule: If a thread is important enough to object to its content, it's important enough to read. If it's not important enough to read, then it's not important enough to respond to. Simple as that. If you're too busy to read everything, I respect that. But if you then start cluttering that same thread with stuff that's already been said, you're just making the problem worse by turning a lively thread into a deluge. If I post an RFC and somebody raises a concern, I'll respond to it. It's totally unnecessary for someone to then post the same concern as if I never did respond, and then turn around and complain that the thread is too cluttery. We can't have it both ways. --Kris --f46d043893479a711f04bde7e769--