From: Steve Nickolas <usotsuki@buric.co>
To: Arthur Krewat <krewat@kilonet.net>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] [OT] Re: earliest Unix roff
Date: Thu, 19 Sep 2019 17:46:13 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1909191745270.12396@frieza.hoshinet.org> (raw)
In-Reply-To: <19f9233f-6f54-46eb-116f-990660ca2a76@kilonet.net>
On Thu, 19 Sep 2019, Arthur Krewat wrote:
> Serious question:
>
> Which is better, creating a whole new binary to put in /usr/bin to do a
> single task, or add a flag to cat?
>
> Which is better, a proliferation of binaries w/standalone source code, or a
> single code tree that can handle slightly different tasks and save space?
>
> :)
>
> art k.
I would argue that the more "Unix" way to do it is have the multiple
binaries. One job, one tool, and chain them together to make bigger
tools.
-uso.
next prev parent reply other threads:[~2019-09-19 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 18:50 Norman Wilson
2019-09-19 19:00 ` Nemo Nusquam
2019-09-19 20:18 ` Larry McVoy
2019-09-19 20:33 ` Arthur Krewat
2019-09-19 20:39 ` Jon Steinhart
2019-09-19 21:46 ` Steve Nickolas [this message]
2019-09-19 21:51 ` Larry McVoy
2019-09-19 20:42 ` [TUHS] " Andy Kosela
2019-09-19 22:44 ` [TUHS] [OT] " Rob Pike
-- strict thread matches above, loose matches on Subject: below --
2019-09-19 21:19 Norman Wilson
2019-09-16 14:51 [TUHS] " Larry McVoy
2019-09-16 14:57 ` Clem Cole
2019-09-16 15:14 ` Richard Salz
2019-09-16 16:10 ` Larry McVoy
2019-09-16 16:16 ` Jon Steinhart
2019-09-16 16:26 ` Larry McVoy
2019-09-16 16:31 ` Richard Salz
2019-09-16 16:45 ` Larry McVoy
2019-09-16 17:19 ` KatolaZ
2019-09-16 17:37 ` Jon Steinhart
2019-09-16 18:09 ` [TUHS] [OT] " KatolaZ
2019-09-16 18:19 ` Jon Steinhart
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=alpine.BSF.2.02.1909191745270.12396@frieza.hoshinet.org \
--to=usotsuki@buric.co \
--cc=krewat@kilonet.net \
--cc=tuhs@minnie.tuhs.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).