From: "John P. Linderman" <jpl.jpl@gmail.com>
To: nliber@gmail.com
Cc: coff@tuhs.org
Subject: [COFF] Re: [TUHS] On Bloat and the Idea of Small Specialized Tools
Date: Sat, 11 May 2024 08:51:27 -0400 [thread overview]
Message-ID: <CAC0cEp_wTKZ5B15g06fKAdaaK6_f3Jx=5N9=8dYftv4V13aWbg@mail.gmail.com> (raw)
In-Reply-To: <CAGg_6+Ov6hYTxQ5M-hEBoOiUQ0UVRP0V+aVi0STKAALLDUGY7g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]
Marc Rochkind used to advise reading the entire UNIX manual cover to cover
each year. The manual was short enough that it could be done in a day or
two. It was a great way to discover commands and system calls you didn't
use every day, and deepen your understanding of the ones you did use every
day. We were in a center that ran PWB UNIX, and the manual was overseen by
Ted Dolotta, who was a stickler for good writing. I can't imagine trying to
do something similar now. -- jpl
On Fri, May 10, 2024 at 7:23 PM Nevin Liber <nliber@gmail.com> wrote:
> On Fri, May 10, 2024 at 11:37 AM Clem Cole <clemc@ccc.com> wrote:
>
>> The key is that not all "bloat" is the same (really)—or maybe one
>> person's bloat is another person's preference.
>>
>
> A lot of "bloat" comes because our systems really aren't focused on
> "discoverability".
>
> While I probably have used "pr" in the past, I've totally forgotten, the
> name "pr" doesn't really help me understand what it is for, and it's just
> one of 982 files in my /usr/bin directory alone. How does one discover it?
>
> It's like using "sed" instead of "head": sure, if you already know "sed",
> you don't need "head", but for English speaking folks who know "tail" is
> there, it would be (and was in the old days) surprising and frustrating not
> to have "head".
>
> If I have a command and I want it to do something slightly different, the
> first place I look is to see if there is a command line option for that. I
> know how to discover that (either --help or the man pages).
>
> GUIs were better at discoverability. The menu at the top made it easy to
> see (and constantly reinforced) what was possible, at least until we got
> into the era of contextual menus, gestures and force presses.
>
> They aren't perfect. I get plenty of dialog boxes which have a check box
> for "Do not show this message again" which I don't dare check, because I
> don't know how to bring up whatever choice it wants me to decide on should
> I need to change it in the future.
>
>
> And once you have users/customers, it's hard to get rid of things, because
> they value stability.
> --
> Nevin ":-)" Liber <mailto:nl <nevin@eviloverlord.com>iber@gmail.com>
> +1-847-691-1404
>
[-- Attachment #2: Type: text/html, Size: 3494 bytes --]
next prev parent reply other threads:[~2024-05-11 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 16:36 [COFF] " Clem Cole
2024-05-10 23:02 ` [COFF] Re: [TUHS] " Steffen Nurpmeso
2024-05-11 9:18 ` [COFF] " Ralph Corderoy
2024-05-11 21:18 ` Steffen Nurpmeso
2024-05-11 21:33 ` Larry McVoy
2024-05-10 23:22 ` [COFF] Re: [TUHS] " Nevin Liber
2024-05-11 9:31 ` [COFF] " Ralph Corderoy
2024-05-11 12:51 ` John P. Linderman [this message]
2024-05-11 13:12 ` [COFF] Re: [TUHS] " Dan Cross
2024-05-11 14:41 ` Bakul Shah via COFF
2024-05-11 15:45 ` Grant Taylor via COFF
2024-05-11 17:18 ` [COFF] " Ralph Corderoy
2024-05-11 21:35 ` [COFF] Re: [TUHS] " Theodore Ts'o
2024-05-12 7:13 ` Gergely Buday
2024-05-12 7:29 ` [COFF] " Ralph Corderoy
2024-05-12 22:23 ` Dave Horsfall
2024-05-11 19:24 ` [COFF] Re: [TUHS] " Clem Cole
2024-05-13 6:20 ` [COFF] " Arno Griffioen via COFF
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='CAC0cEp_wTKZ5B15g06fKAdaaK6_f3Jx=5N9=8dYftv4V13aWbg@mail.gmail.com' \
--to=jpl.jpl@gmail.com \
--cc=coff@tuhs.org \
--cc=nliber@gmail.com \
/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).