From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Thanks for Virtuallyfun! (was Re: Happy birthday, 386BSD!)
Date: Sun, 14 Jul 2019 15:19:07 -0400 (EDT) [thread overview]
Message-ID: <20190714191907.3B48618C091@mercury.lcs.mit.edu> (raw)
> From: Adam Thornton
> something designed for single-threaded composible text-filtering
> operations is now running almost all of the world's multithreaded
> user-facing graphical applications, but that's the vagaries of history
> for you.
It's a perfect example of my aphorism, "The hallmark of truly great
architecture is not how well it does the things it was designed to do, but how
well it does things it was never expected to handle."
Noel
next reply other threads:[~2019-07-14 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 19:19 Noel Chiappa [this message]
2019-07-15 9:33 ` Wesley Parish
-- strict thread matches above, loose matches on Subject: below --
2019-07-14 5:56 [TUHS] Happy birthday, 386BSD! Dave Horsfall
2019-07-14 6:53 ` Jason Stevens
2019-07-14 8:17 ` [TUHS] Thanks for Virtuallyfun! (was Re: Happy birthday, 386BSD!) Michael Huff
2019-07-14 9:07 ` Jason Stevens
2019-07-14 17:47 ` Adam Thornton
2019-07-15 1:54 ` Jason Stevens
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=20190714191907.3B48618C091@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).