The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Kurt H Maier <khm@sciops.net>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] cat -v and other complaints
Date: Mon, 3 Sep 2018 14:46:14 -0700	[thread overview]
Message-ID: <DD463A42-AF09-46C2-99F6-F2328DDDC4EF@bitblocks.com> (raw)
In-Reply-To: <20180903204115.GC99551@wopr>

On Sep 3, 2018, at 1:41 PM, Kurt H Maier <khm@sciops.net> wrote:
> 
> Acme is a bad citizen in similar ways, but as I said, I suspect that's
> because it was intended to supplant Rio rather than infect it.

I’m still not clear on why you think acme is a bad citizen. If anything it
makes its windows more accessible to other tools. Unlike emacs or vim
or any IDE. What could acme have differently or what other editor is
not a “bad citizen”.

> When people talk about "the unix way," they usually hyperfocus on "do
> one thing well" and leave composability by the wayside, and that's a
> shame, because that's where the real power comes from.  "Do one thing
> well" is a method to achieve quality when you're building a piece of a
> well-integrated system.  If you're not building a well-integrated
> system, you *can't* "do one thing well," because you've signed on to do
> everything, come hell or high water.

Composability is implicitly the key point in “the Unix way” but typically
editors are not very composable. Or composable in a different domain.
Similarly GUI. Once you add a human in your composition, further
composability falls apart! A human being the ultimate “do everything”
kitchen sink:-)

The question is what can be done to improve composability beyond the
“Unix way” or plan9 way.

  reply	other threads:[~2018-09-03 21:47 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 14:25 Clem Cole
2018-08-29 22:34 ` Dave Horsfall
2018-08-29 23:36   ` Larry McVoy
2018-08-30  1:14     ` Clem cole
2018-08-30  1:15       ` Clem cole
2018-08-30  2:43       ` Kevin Bowling
2018-08-30  2:59         ` George Michaelson
2018-08-31  0:27         ` Dave Horsfall
2018-08-31  0:41           ` Dan Cross
2018-08-31  1:58             ` Larry McVoy
2018-08-31 11:38           ` ron
2018-08-31 14:41           ` [TUHS] UNIX System names - since UNIX was a Trademark Clem Cole
2018-08-31 15:13             ` Eric Wayte
2018-08-31 15:17             ` William Pechter
2018-08-31 15:25               ` Clem Cole
2018-09-01  0:10               ` John P. Linderman
2018-09-01  0:18                 ` ron
2018-09-01  0:55                   ` Nemo
2018-09-01  7:37                     ` Dave Horsfall
2018-09-01 13:54                       ` Nemo
2018-09-01 17:03                       ` Paul Winalski
2018-09-03  1:14                         ` Robert Brockway
2018-09-30 20:57                 ` Lyndon Nerenberg
2018-10-01 16:26                   ` Paul Winalski
2018-09-01  0:00             ` Dave Horsfall
2018-08-31 21:56 ` [TUHS] cat -v and other complaints Cág
2018-09-01  3:37   ` Andrew Warkentin
2018-09-03 18:04     ` Cág
2018-09-03 18:11       ` Kurt H Maier
2018-09-03 18:56         ` Cág
2018-09-04  6:10           ` Andy Kosela
2018-09-04  6:41             ` ron minnich
2018-09-04  9:34               ` Andy Kosela
2018-09-04 10:23                 ` Dan Cross
2018-09-04 14:22                 ` ron minnich
2018-09-06 20:02                   ` Andy Kosela
2018-09-06 20:49                     ` ron minnich
2018-09-06 21:55                       ` Andy Kosela
2018-09-07  1:59                         ` Dan Cross
2018-09-07  4:40                           ` Andy Kosela
2018-09-30 21:32           ` Lyndon Nerenberg
2018-09-03 20:08         ` Bakul Shah
2018-09-03 20:41           ` Kurt H Maier
2018-09-03 21:46             ` Bakul Shah [this message]
2018-09-04  0:52               ` Kurt H Maier
2018-09-06 20:29 Norman Wilson
2018-09-06 22:16 ` Andy Kosela
2018-09-08 12:02 [TUHS] [TUHS} " Doug McIlroy
2018-09-08 13:36 ` Will Senn
2018-09-08 14:22   ` [TUHS] " Ralph Corderoy
2018-09-08 16:10     ` Arthur Krewat

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=DD463A42-AF09-46C2-99F6-F2328DDDC4EF@bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=khm@sciops.net \
    --cc=tuhs@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).