From: doug@cs.dartmouth.edu (Doug McIlroy)
Subject: [TUHS] mail tuhs@minnie.tuhs.org
Date: Fri, 23 Mar 2018 21:26:29 -0400 [thread overview]
Message-ID: <201803240126.w2O1QTB5109348@tahoe.cs.Dartmouth.EDU> (raw)
[TUHS] long lived programs (was Re: RIP John Backus
> Every year someone takes some young hotshot and points them at some
"impossible" thing and one of them makes it work. I don't see that
changing.
Case in point.
We hired Tom Killian, a young high-energy physicist disenchanted
with contributing to hundred-author papers. He'd done plenty of
instrument programming, but no operating systems. So, high-energy
as he was, he cooked up an exercise to get his feet wet.
The result: /proc
Doug
next reply other threads:[~2018-03-24 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-24 1:26 Doug McIlroy [this message]
2018-03-24 1:54 ` Larry McVoy
2018-03-27 9:20 ` Michael-John Turner
-- strict thread matches above, loose matches on Subject: below --
2018-01-22 12:31 [TUHS] !mail tuhs@minnie.tuhs.org Doug McIlroy
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=201803240126.w2O1QTB5109348@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
/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).