From: Cág <ca6c@bitmessage.ch>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] cat -v and other complaints
Date: Fri, 31 Aug 2018 16:56:36 -0500 [thread overview]
Message-ID: <20180831215636.-eCEx%ca6c@bitmessage.ch> (raw)
In-Reply-To: <CAC20D2ODDO+OTUf8wA4bXu9M5M0kswJqT97qRAnV9EOzMGKRvQ@mail.gmail.com>
Not completely on-topic, in my opinion one of the reasons Plan9 failed
was the fact that it presented itself overly idealistic, occasionally
sacrificing usability -- maybe it's because of coming from a Unix system
like Berkeley or IRIX, in which case, I think Brian Kernighan said, "if
you'll think of it as Unix, you'll often be frustrated because something
doesn't exist or works differently." On the one hand the `cat -v` and
some other concerns (like columnated ls(1) output) are valid, and very
well understood. On the other -- lack of find(1), shell history, and
vi are not. Well, to me at least. Both acme and sam seem to have found
its fanbase.
Note, when I'm saying failed I mean commercially. As a research
operating system, or, dare I say, esoteric, because in some way it was
and still is esoteric, it succeeded as none of the others, with its
impact going through this day.
--
caóc
next prev parent reply other threads:[~2018-08-31 21:57 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 ` Cág [this message]
2018-09-01 3:37 ` [TUHS] cat -v and other complaints 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
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=20180831215636.-eCEx%ca6c@bitmessage.ch \
--to=ca6c@bitmessage.ch \
--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).