From: Bakul Shah <bakul@iitbombay.org>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler)
Date: Fri, 3 Feb 2023 09:45:59 -0800 [thread overview]
Message-ID: <B5EE26EC-68AB-479F-A69F-A1429FE443CB@iitbombay.org> (raw)
In-Reply-To: <CAEoi9W4x2wX3zTCgRKEoQ+qG=QiqR1piqeszh8_L6py0aAAm+g@mail.gmail.com>
On Feb 3, 2023, at 8:41 AM, Dan Cross <crossd@gmail.com> wrote:
>
> But TUHS is clearly meant to be a Unix history list, not a "list about
> new systems where we can ask about history because that helps us build
> those new systems". In that sense, I'm not looking for COFF or a retro
> or classic computer list, either, but for something explicitly modern
> yet informed by history.
>
> I don't believe such a thing actually exists.
I’m not aware of one. May be comp.arch comes close. Any new list
will have difficulty attracting the right kind of people. TUHS, COFF are
rather unix oriented. If you mean *software systems*, I suspect the
field is still too green to have a proper systematic analysis or
established engineering principles. We still seem to be in the “Cambrian
explosion” phase where every new complex system is a new species.
next prev parent reply other threads:[~2023-02-03 17:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 19:02 [TUHS] Typesetter C compiler Noel Chiappa
2023-02-02 21:57 ` [TUHS] " Jonathan Gray
2023-02-03 0:43 ` Jonathan Gray
2023-02-02 22:36 ` [TUHS] Proper use of TUHS (was Re: Typesetter C compiler) Dan Cross
2023-02-02 22:41 ` [TUHS] " Larry McVoy
2023-02-02 22:47 ` Jim Capp
2023-02-03 1:44 ` Dave Horsfall
2023-02-03 13:17 ` Alan D. Salewski
2023-02-03 13:55 ` Larry McVoy
2023-02-06 20:02 ` Chris Hanson
2023-02-03 14:11 ` Chet Ramey
2023-02-03 14:15 ` Larry McVoy
2023-02-03 16:39 ` Dan Cross
2023-02-03 16:54 ` Larry McVoy
2023-02-03 17:08 ` Dan Cross
2023-02-03 17:11 ` Steve Nickolas
2023-02-03 17:26 ` [TUHS] move to COFF " Will Senn
2023-02-03 17:31 ` [TUHS] " Will Senn
2023-02-03 17:45 ` Bakul Shah [this message]
2023-02-05 10:42 ` [TUHS] " steve jenkin
2023-02-04 8:03 ` [TUHS] A List for New Systems Influenced by History. (Was: Proper use of TUHS) Ralph Corderoy
2023-02-04 13:56 ` [TUHS] " Larry McVoy
2023-02-04 17:31 ` [TUHS] Re: A List for New Systems Influenced by History Angel M Alganza
2023-02-03 6:36 ` [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler) Lars Brinkhoff
2023-02-04 22:38 ` Tomasz Rola
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=B5EE26EC-68AB-479F-A69F-A1429FE443CB@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=crossd@gmail.com \
--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).