From: scj@yaccman.com (Steve Johnson)
Subject: [TUHS] long lived programs (was Re: RIP John Backus
Date: Fri, 23 Mar 2018 15:02:57 -0700 [thread overview]
Message-ID: <11b473d966bf0dd48f5f1c10e55974173010e5aa@webmail.yaccman.com> (raw)
In-Reply-To: <CANCZdfpJbW0jsfjHs6JdqyqVreV0CPuHFqe=0mP_DdMp_X5EYQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Reminds me a bit of the old saying: "This is George Washington's
Axe. Of course, it's had six new handles and four new heads since he
owned it..."
Steve
----- Original Message -----
From:
"Warner Losh" <imp at bsdimp.com>
To:
"Clem Cole" <clemc at ccc.com>
Cc:
"TUHS main list" <tuhs at minnie.tuhs.org>
Sent:
Fri, 23 Mar 2018 15:36:02 -0600
Subject:
Re: [TUHS] long lived programs (was Re: RIP John Backus
On Fri, Mar 23, 2018 at 3:23 PM, Clem Cole <clemc at ccc.com [1]>
wrote:Which bringing this back to UNIX. Linux is the UNIX
disruptor - which is great. Linux keeps 'UNIX' alive and getting
better. I don't see an economic reason to replace it, but who
knows. Maybe that's what the new good folks at Goggle, Amazon, Intel
or some University is doing. But so far, the economics is not
there.
Speaking of how ancient code works... There's still AT&T code dating
to v5 or older in *BSD.... It's been updated, improved upon, parts
replaced, etc. But there's still some bits dating all the way back to
those early times. Having competition from Linux is great and keeps
the BSDs honest...
Warner
ᐧ
Links:
------
[1] mailto:clemc at ccc.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180323/3aaf806f/attachment-0001.html>
next prev parent reply other threads:[~2018-03-23 22:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.21.1521314548.3788.tuhs@minnie.tuhs.org>
2018-03-17 20:14 ` [TUHS] " Paul McJones
2018-03-17 22:27 ` Steve Johnson
2018-03-22 21:05 ` [TUHS] long lived programs (was " Bakul Shah
2018-03-22 21:35 ` Clem Cole
2018-03-23 19:28 ` Bakul Shah
2018-03-23 19:44 ` Larry McVoy
2018-03-23 21:23 ` Clem Cole
2018-03-23 21:36 ` Warner Losh
2018-03-23 22:02 ` Steve Johnson [this message]
2018-03-26 13:43 ` Tim Bradshaw
2018-03-26 16:19 ` Paul Winalski
2018-03-26 16:41 ` Arthur Krewat
2018-03-26 19:53 ` Larry McVoy
2018-03-27 1:08 ` Clem Cole
2018-03-26 19:04 ` Bakul Shah
2018-03-27 1:21 ` Steve Johnson
2018-03-27 1:46 ` Clem Cole
2018-03-23 10:43 ` Tim Bradshaw
[not found] ` <CAC20D2P1CZwaD0uJpMhWg11muDeH9rEn3X+AUjXvwMKsNjs7ng@mail.gmail.com>
2018-03-26 0:53 ` [TUHS] Fwd: " Clem Cole
2018-03-23 2:53 [TUHS] " Doug McIlroy
2018-03-23 18:27 ` Bakul Shah
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=11b473d966bf0dd48f5f1c10e55974173010e5aa@webmail.yaccman.com \
--to=scj@yaccman.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).