From: ches@cheswick.com (William Cheswick)
Subject: [TUHS] Discuss of style and design of computer programs from a user standpoint
Date: Sun, 7 May 2017 14:50:52 -0400 [thread overview]
Message-ID: <5D559802-6D6E-4668-9CA5-141B071BC535@cheswick.com> (raw)
In-Reply-To: <201705071819.v47IJ24H002013@coolidge.cs.Dartmouth.EDU>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
> On 7May 2017, at 2:19 PM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
>
> Not genius. Experience.
It’s the pipe that was genius. When I first heard the idea, I thought it was preposterous. My
programs’ outputs were designed for the line printer, with carriage control characters. How
could this idea be useful?
These tools are powerful--I co-founded a company out of network probe software mostly designed
around filters. And it scales beautifully to multi-core computing. I had movie visualization software
suddenly nearly double in speed one day. They had doubled the number of CPUs in the ferric cluster.
My favorite filter: the unsort (or scramble) command.
Honeyman’s “idiom” command:
sort | uniq -c | sort -rn
next prev parent reply other threads:[~2017-05-07 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 18:19 Doug McIlroy
2017-05-07 18:50 ` William Cheswick [this message]
2017-05-07 22:03 ` Larry McVoy
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=5D559802-6D6E-4668-9CA5-141B071BC535@cheswick.com \
--to=ches@cheswick.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).