From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] doc: add technical/whyperl
Date: Thu, 09 Apr 2020 01:14:22 +0000 [thread overview]
Message-ID: <87ftddihox.fsf@kyleam.com> (raw)
In-Reply-To: <20200408222607.GA4741@dcvr>
Eric Wong <e@yhbt.net> writes:
> Kyle Meyer <kyle@kyleam.com> wrote:
>
>> Eric Wong <e@yhbt.net> writes:
>>
>> > +As always, comments and corrections and additions welcome at
>>
>> s/welcome/are welcome/ ?
>
> Umm... I guess? Would omitting "are" would only be valid
> if there were a single item?
>
> As always, $FOO welcome at
I guess dropping an "is" in the singular case sounds a little better to
my ears than dropping "are" in the plural case. I think the original
was fine, though. I stumbled on it for whatever reason and would write
"are" there myself, but it probably wasn't worth me noting, even if I
hid behind a "?" :>
> Upon a second read of the original, having "and" twice doesn't
> read well to me. So final form should probably be:
>
> As always, comments, corrections and additions are welcome at
Yes, I too would prefer dropping the first "and".
>> > + performance and memory use are predictable and does not
>>
>> s/does/do/
>>
>> > + require GC tuning by the user.
>
> I think "does" reads better, there, but the sentence runs on
> for too long. I don't think the GC part needs to be there(*)
Hmm, okay. I think I misidentified what the intended subject was there.
I took the subject as "performance and memory use", which case there is
a tense mismatch (and it sticks out because "are" is used in the
previous sentence). And it doesn't matter because it's getting cut :)
Thanks for writing up this rationale.
next prev parent reply other threads:[~2020-04-09 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 9:49 [PATCH] doc: add technical/whyperl Eric Wong
2020-04-08 0:41 ` Kyle Meyer
2020-04-08 22:26 ` Eric Wong
2020-04-09 1:14 ` Kyle Meyer [this message]
[not found] ` <87r1wyjlop.fsf@vuxu.org>
2020-04-08 22:17 ` Eric Wong
2020-04-08 22:37 ` Leah Neukirchen
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftddihox.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@yhbt.net \
--cc=meta@public-inbox.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://80x24.org/public-inbox.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).