From: Chet Ramey <chet.ramey@case.edu>
To: Will Senn <will.senn@gmail.com>, tuhs@tuhs.org
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Fri, 27 Jan 2023 09:08:13 -0500 [thread overview]
Message-ID: <b5860440-6be7-662b-95f1-184a13b0bd74@case.edu> (raw)
In-Reply-To: <45987281-a06d-810e-9689-5a8ae2c63a63@gmail.com>
On 1/26/23 11:07 PM, Will Senn wrote:
> but I really don't know nothing about NeXT, it's boxes, or what I'm really
> wondering about - its relationship with unix (although I'm pretty sure
> there is one). I know that Sun was working with them on OpenStep and
> OpenStep and the NeXT cube were predecessors to my favorite contemporary
> system (my Mac), but that's about it. So, how does NeXT fit into the unix
> world? And was it all that? I remember after talking to them that I really,
> really wanted one...
NeXTs were really nice boxes. The environment was basically Mach + 4.3BSD +
Display Postscript + Objective C + the libraries and frameworks that became
macOS Carbon and Cocoa + their GUI. I had one for a while, and wish I still
did for old times' sake.
NeXT was Steve Jobs's company, and Apple acquired them to make the NeXT OS
the basis of MacOS X. That is a very interesting story itself.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
next prev parent reply other threads:[~2023-01-27 14:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:38 Noel Chiappa
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 [this message]
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=b5860440-6be7-662b-95f1-184a13b0bd74@case.edu \
--to=chet.ramey@case.edu \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.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).