Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Bakul Shah via COFF <coff@tuhs.org>
To: Dan Cross <crossd@gmail.com>
Cc: coff@tuhs.org
Subject: [COFF] Re: [TUHS] On Bloat and the Idea of Small Specialized Tools
Date: Sat, 11 May 2024 07:41:56 -0700	[thread overview]
Message-ID: <F3936873-25F9-4076-8C92-15AE07CB23CF@iitbombay.org> (raw)
In-Reply-To: <CAEoi9W7FbGZFhiddHWWqdivGFfgFAj9nsUApomswfP56rqTMpQ@mail.gmail.com>

On May 11, 2024, at 6:12 AM, Dan Cross <crossd@gmail.com> wrote:
> 
> 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?
> 
> This is a fantastic question. At one point, I went through every
> command in /bin and /usr/bin and figured out what it did. That was a
> tremendously useful exercise, but that was in the days when the total
> number of commands in those directories numbered in the low hundreds;
> 982 is a lot.

I did this when I first encountered Unix (v7): tried out most things
described in every command's man page! I still occasionally scan the
the [s]bin directories. But it seems there are fewer and fewer new
programs that can be used in cmd pipelines. The situation is a bit
like Sanskrit (built from a relatively small set of root words but
infinitely combinable) and prakrits, vernacular dialects that are
not so flexible but more practical.



  reply	other threads:[~2024-05-11 14:42 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   ` [COFF] Re: [TUHS] " John P. Linderman
2024-05-11 13:12   ` Dan Cross
2024-05-11 14:41     ` Bakul Shah via COFF [this message]
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=F3936873-25F9-4076-8C92-15AE07CB23CF@iitbombay.org \
    --to=coff@tuhs.org \
    --cc=bakul@iitbombay.org \
    --cc=crossd@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).