patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Valentin Gagarin <valentin@gagarin.work>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH] Documentation: reword the distinctive feature of shared state
Date: Fri, 19 Jun 2026 16:54:26 +0200	[thread overview]
Message-ID: <87a4sqa8d9.fsf@alyssa.is> (raw)
In-Reply-To: <c30345fc-4606-4275-81fe-49fa4de3b83d@gagarin.work>

[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]

Valentin Gagarin <valentin@gagarin.work> writes:

>>> - s/backed up and//
>>>
>>>    The difficulty of backing up is a specific instance of the
>>>    fragmentation problem.  But this is likely only evident to Qubes
>>>    users.  We can expect most readers to know about it theoretically at
>>>    best.  While it's not wrong to have this sort of anchor, keeping it
>>>    risks diluting the main message.
>> 
>> I'm concerned that removing the more specific verbs here might make it
>> more difficult to understand /why/ treating the system as a whole is
>> desirable.  We don't have to be so specific as to call out backups or
>> management, but I think without talking about something more specific,
>> even if that's just "thinking", as in "one only needs to think about a
>> single system", it loses its motivation.
>
> Yes, what we're trying to convey here feels tricky to get right.  Not 
> sure "thinking of" is more specific than "treating", but maybe it better 
> gets across a sentiment of "conceptualising" (in the sense of: mentally 
> grasping).  In my drafting I was mainly focused on the interaction with 
> the system, since I came from the original which worked with examples of 
> handling the system and thus *implied* some thinking.  Maybe thinking is 
> just the right thing.  At least this sounds perfectly fine to me:
>
>      This means that the system can be thought of as a whole, rather than
>      many virtual machines each becoming a system of its own.
>
> One could argue that thinking about a system is a very specific 
> interaction we perform very often...
>
> Feel free to fix it up like that, otherwise I'll give it another round 
> of ideas.

Thinking about it some more, I wonder if maybe my emphasis on verbs was
misplaced.  The underlying thing I wanted to communicate is the feeling,
and I was relying on the verbs to connote those feelings to the reader.
The relevant feelings here are "burdened" and "overwhelmed".  Perhaps
there's a better way to get those across, either directly or indirectly.
What do you think?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2026-06-19 14:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 13:24 [PATCH] Documentation: reword the distinctive feature of shared state Valentin Gagarin
2026-06-17 16:55 ` Alyssa Ross
2026-06-17 19:40   ` Valentin Gagarin
2026-06-19 14:54     ` Alyssa Ross [this message]
2026-06-22  9:55 ` [PATCH v2 1/2] " Valentin Gagarin
2026-06-22  9:55   ` [PATCH v2 2/2] Documentation: sketch the threat model on the front page Valentin Gagarin
2026-06-22 13:26     ` Alyssa Ross
2026-06-22 17:55       ` Valentin Gagarin
2026-06-24  8:57     ` Alyssa Ross
2026-06-24 12:18     ` Alyssa Ross
2026-06-22 13:24   ` [PATCH v2 1/2] Documentation: reword the distinctive feature of shared state Alyssa Ross
2026-06-22 13:28   ` Alyssa Ross

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=87a4sqa8d9.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=devel@spectrum-os.org \
    --cc=valentin@gagarin.work \
    /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://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

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).