From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Wed, 25 Jan 2023 15:38:05 -0500 (EST) [thread overview]
Message-ID: <20230125203805.4762218C083@mercury.lcs.mit.edu> (raw)
> From: Lars Brinkhoff
> It's my understanding it was started by Bob Scheifler of the CLU group.
Yes, that's correct. (Bob's office was right around the corner from me -
although I had very little knowledge of what his group was up to; I was too
busy with other things.)
I have this vague memory that his version was actually written in CLU? Can
that be correct? It would make sense, since that group was so focused on CLU
- but maybe not, see below.
X must have been done after LCS got the 750 farm (on which we ran 4.1c, to
start with) - although I don't know what kind of terminals they were using to
run X on - we didn't have any bit-mapped displays on them, I'm pretty sure.
Although maybe it was later, once Micro-Vaxes appeared?
I have this vague memory that it was based (perhaps only in design, not code
re-use) on a window system done at Stanford {looks}; yes, W (hence 'X'):
https://en.wikipedia.org/wiki/W_Window_System
The X paper listed there:
https://dl.acm.org/doi/pdf/10.1145/22949.24053
doesn't say anything about the implementation, so maybe that vague
memory/assumption that I had that it was originally written in CLU is wrong.
Liskov's 'History of CLU' paper, which lists things done in CLU, doesn't
mention it, so I must have been confused?
Do any of the really early versions of X (and W) still exist?
Noel
next reply other threads:[~2023-01-25 20:38 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:38 Noel Chiappa [this message]
2023-01-25 21:25 ` Clem Cole
2023-01-26 6:30 ` Lars Brinkhoff
2023-01-26 10:56 ` Ralph Corderoy
2023-01-26 12:01 ` arnold
2023-01-26 13:25 ` Lars Brinkhoff
2023-01-26 15:28 ` [TUHS] " josh
2023-01-26 16:07 ` [TUHS] " segaloco via TUHS
2023-01-26 16:48 ` emanuel stiebler
2023-01-26 21:19 ` segaloco via TUHS
2023-01-26 22:51 ` Andy Kosela
2023-01-27 0:48 ` segaloco via TUHS
2023-01-27 4:07 ` Will Senn
2023-01-27 14:08 ` Chet Ramey
2023-01-27 14:49 ` Ron Natalie
2023-01-27 15:53 ` Dan Cross
2023-01-27 16:12 ` [TUHS] NEXTSTEP 486 [was " Charles H Sauer (he/him)
2023-01-27 14:17 ` [TUHS] " Ralph Corderoy
2023-01-27 13:56 ` Ralph Corderoy
2023-01-27 14:54 ` Ron Natalie
2023-01-27 16:10 ` Larry McVoy
2023-01-28 22:15 ` Dave Horsfall
2023-01-29 0:31 ` Kevin Bowling
2023-01-29 11:07 ` emanuel stiebler
2023-01-27 21:42 ` Tom Perrine
2023-01-28 2:18 ` Larry McVoy
2023-01-28 2:49 ` Tom Perrine
2023-01-26 6:32 ` Lars Brinkhoff
2023-01-26 9:45 ` emanuel stiebler via TUHS
-- strict thread matches above, loose matches on Subject: below --
2023-01-25 1:46 [TUHS] " Will Senn
2023-01-25 7:45 ` [TUHS] " segaloco via TUHS
2023-01-25 8:00 ` Lars Brinkhoff
2023-01-25 16:41 ` Rich Salz
2023-01-25 19:53 ` Theodore Ts'o
2023-01-25 20:04 ` Dan Cross
2023-01-25 20:23 ` Larry McVoy
2023-01-25 20:27 ` Chet Ramey
2023-01-27 4:49 ` Theodore Ts'o
2023-01-27 18:05 ` Henry Mensch
2023-01-27 18:24 ` Charles H Sauer (he/him)
2023-01-26 13:17 ` Marc Donner
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=20230125203805.4762218C083@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).