9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Mon, 27 Jul 2020 13:01:18 -0700	[thread overview]
Message-ID: <C971DE8A14D43FC4F0E4D1213FBD1EB4@eigenstate.org> (raw)
In-Reply-To: <44A75FA2-F810-45DA-8264-6DBB810C53F1@stanleylieber.com>

> part of the problem for new users is that plan 9 assumes any user
> understands the fundamentals of computing at a deeper level than even
> "power users" of other systems.  this was already a stumbling block in
> the 1990s, and it has only deepened as operating systems drag the user
> experience farther and farther away from the underlying mechanisms.

That's a part of it. But a part of it is that there's a lot
of documentation that either sucks or doesn't exist. For
example, I'm not aware of anything that documents the rather
unique ways we handle scrolling, where how far up the window
you are affects how quick the scrolling goes.

NDB also seems like a constant source of confusion -- and
while it largely makes sense when you get it, I don't think
that the manpages lay it out very well.

So, while I don't think we want to fix the assumption that
you understand how your computer works, a combination of
picking better defaults and documenting things better is
something that *I* will appreciate, and I've been around
9front for a while.



  parent reply	other threads:[~2020-07-27 20:01 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  9:09 sirjofri+ml-9front
2020-07-27  9:56 ` [9front] " hiro
2020-07-27 15:10 ` Amavect
2020-07-27 15:54   ` Stanley Lieber
2020-07-27 15:58 ` ori
2020-07-27 17:01   ` William Gunnells
2020-07-27 17:29     ` Stanley Lieber
2020-07-27 18:09       ` William Gunnells
2020-07-27 20:01       ` ori [this message]
2020-07-27 21:22         ` Ethan Gardener
2020-07-28 19:10           ` cinap_lenrek
2020-07-29 22:36             ` Ethan Gardener
2020-07-27 22:06         ` Anthony Martin
2020-07-27 22:21           ` Stanley Lieber
2020-07-27 23:46             ` ori
2020-07-27 22:17         ` Stanley Lieber
2020-07-27 22:47           ` Kurt H Maier
2020-07-27 23:50             ` ori
2020-07-28  4:56               ` sirjofri+ml-9front
2020-07-28 10:18                 ` hiro
2020-07-28 11:27                   ` sirjofri+ml-9front
2020-07-28 12:14                     ` hiro
2020-07-28 13:08                       ` sirjofri+ml-9front
2020-07-28 14:16                         ` hiro
2020-07-28 15:01                           ` Stanley Lieber
2020-07-28 15:12                             ` ori
2020-07-28 15:46                               ` Stanley Lieber
2020-07-28 17:25                                 ` hiro
2020-07-28 17:37                                 ` ori
2020-07-28 17:43                                   ` Kurt H Maier
2020-07-28 15:11                         ` ori
2020-07-28 11:29                   ` sirjofri+ml-9front
2020-07-29 17:10                     ` ori
2020-07-30  1:02             ` sl
2020-07-28  9:48           ` hiro
2020-07-30 18:12 ` magma698hfsp273p9f
2020-07-30 18:48   ` kvik
2020-07-30 18:54   ` ori
2020-07-30 19:28     ` Eckard Brauer
2020-07-30 19:59     ` Romano
2020-07-31 13:44       ` kvik
2020-07-31 13:51         ` Stanley Lieber
2020-08-01 15:42         ` Ethan Gardener
2020-07-30 19:15   ` Kurt H Maier
2020-07-31 10:59     ` Ethan Gardener
2020-08-03 18:50       ` magma698hfsp273p9f
2020-08-04 17:13         ` Ethan Gardener
     [not found] <98A6B5A900B5E1660221CE63074D0920@ewsd.inri.net>
2020-07-30  2:14 ` ori
2020-07-30  3:06   ` Stanley Lieber
2020-07-30  3:12     ` Michael Misch
2020-07-30  8:19       ` hiro
2020-07-30  8:58         ` Kurt H Maier
2020-07-30 12:03       ` Ethan Gardener

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=C971DE8A14D43FC4F0E4D1213FBD1EB4@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.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.
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).