From: Jim Capp <jcapp@anteil.com>
To: Larry McVoy <lm@mcvoy.com>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler)
Date: Thu, 2 Feb 2023 17:47:50 -0500 [thread overview]
Message-ID: <82A9B97D-9ED2-4DFF-A1DE-765437ACCE9B@anteil.com> (raw)
In-Reply-To: <20230202224136.GI30555@mcvoy.com>
I love the topics and people on TUHS.
But I also subscribed to COFF so I could pick up on interesting scraps not suitable for TUHS.
> On Feb 2, 2023, at 5:41 PM, Larry McVoy <lm@mcvoy.com> wrote:
>
> On Thu, Feb 02, 2023 at 05:36:44PM -0500, Dan Cross wrote:
>>> On Thu, Feb 2, 2023 at 2:02 PM Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>>> [snip] I don't
>>> have the energy to look through the tons of opinion posts about recent
>>> programming styles, to find the posts about actual Unix history which related
>>> to that compiler,
>>> [snip]
>>
>> On a semi-related note....
>>
>> I have found TUHS a valuable resource, not just for discussing Unix
>> history, but for gaining a deeper understanding of systems which
>> informs my present and that I imagine will influence my future work as
>> well.
>>
>> However, lately it has become clear that this is not always a welcome
>> use of the list. I don't think COFF is universally appropriate for
>> that either.
>
> COFF lacks critical mass. It's a common problem, you have a mailing list
> with enough people that it is interesting and it gets too noisy so the
> admin creates a more chatty list and only a small subset of the people
> pick that up. I don't know how to fix that.
>
>> So, the question becomes: what _is_ that forum, if such a thing exists at all?
>
> Well, Hacker News was supposed to be really system-y. I tried it for a while,
> there was some good stuff there but it was drowned out by wannabe hackers
> talking about trivial stuff as if it were interesting. So I gave up.
>
> If you find a Unix/Systems sort of forum, that actually has something to
> say, let us know.
> --
> ---
> Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2023-02-02 22:48 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 [this message]
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 ` [TUHS] " Bakul Shah
2023-02-05 10:42 ` 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=82A9B97D-9ED2-4DFF-A1DE-765437ACCE9B@anteil.com \
--to=jcapp@anteil.com \
--cc=jnc@mercury.lcs.mit.edu \
--cc=lm@mcvoy.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).