From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Roman Perepelitsa" <roman.perepelitsa@gmail.com>,
"Ray Andrews" <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: Counting characters in command output?
Date: Thu, 15 Feb 2024 09:30:27 -0500 [thread overview]
Message-ID: <c71b3dca-d39d-4e2f-98e7-34a22295a48b@app.fastmail.com> (raw)
In-Reply-To: <CAN=4vMop_MyF0jyVq14Jd1TXRked9vmeUxOK+xXjPMJGnM0UBg@mail.gmail.com>
On Thu, Feb 15, 2024, at 4:50 AM, Roman Perepelitsa wrote:
> On Wed, Feb 14, 2024 at 4:37 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>>
>> What are the vectors? First must be logical necessity, second
>> consistency -- avoid strange exceptions -- third and fourth would
>> be helpfulness and tradition, with old-school guys favoring
>> tradition and guys like me favoring helpfulness.
>
> In any debate between tradition and helpfulness, ensure your
> counterpart agrees with this perspective. Should they present
> arguments they consider essential for necessity and consistency, and
> you categorize them merely as "tradition," dialogue ceases. From their
> standpoint, your stance appears at best inconsistent, or at worst,
> vague, and you fail to recognize their points even when clearly
> outlined.
I would push it further: The worst-case perception would be one of ignorant arrogance. Compatibility is not tradition, but calling it so suggests a dismissive, uncharitable belief that there are no plausible reasons for it -- only a stubborn preference for How Things Used to Be. People rarely respond well when they think they're being called sclerotic morons.
>> I wish there were enough of us on this list to put things to a vote
>> sometimes [...]
>
> For anything to happen, somebody has to do the work. There is no point
> in voting if the vote has no consequences: it's not an obligation for
> anybody to do the work, nor does any work require an approval from
> voters.
Voting is a poor mechanism for building consensus, in any case.
https://producingoss.com/en/consensus-democracy.html#when-to-vote
--
vq
next prev parent reply other threads:[~2024-02-15 14:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 20:38 Mark J. Reed
2024-02-13 20:41 ` Roman Perepelitsa
2024-02-14 0:45 ` Mark J. Reed
2024-02-14 6:49 ` Roman Perepelitsa
2024-02-14 13:56 ` Mark J. Reed
2024-02-14 15:36 ` Ray Andrews
2024-02-14 15:58 ` Mark J. Reed
2024-02-14 16:30 ` Ray Andrews
2024-02-15 14:34 ` Lawrence Velázquez
2024-02-15 9:50 ` Roman Perepelitsa
2024-02-15 14:30 ` Lawrence Velázquez [this message]
2024-02-15 15:29 ` Ray Andrews
2024-02-15 16:16 ` Roman Perepelitsa
2024-02-15 16:55 ` Ray Andrews
2024-02-15 14:53 ` Ray Andrews
2024-02-16 1:53 ` Bart Schaefer
2024-02-16 4:53 ` Lawrence Velázquez
2024-02-16 18:03 ` Bart Schaefer
2024-02-16 18:38 ` Mark J. Reed
2024-02-16 19:36 ` Bart Schaefer
2024-02-16 19:37 ` Lawrence Velázquez
2024-02-16 21:06 ` Mikael Magnusson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c71b3dca-d39d-4e2f-98e7-34a22295a48b@app.fastmail.com \
--to=larryv@zsh.org \
--cc=rayandrews@eastlink.ca \
--cc=roman.perepelitsa@gmail.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).