The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Will Senn <will.senn@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Setting up an X Development Environment for Mac OS
Date: Fri, 27 Jan 2023 10:53:55 -0500	[thread overview]
Message-ID: <CAEoi9W7WyNDHLmr5BqLxyK3sQSX0VTU6FZG32z5n20O6iAzx8Q@mail.gmail.com> (raw)
In-Reply-To: <45987281-a06d-810e-9689-5a8ae2c63a63@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2876 bytes --]

On Thu, Jan 26, 2023 at 11:08 PM Will Senn <will.senn@gmail.com> wrote:
> [snip]
> I also remember that they were bemoaning having to give up their NeXT
> boxes for racks and racks of some other machine to do equivalent work
> (at the time, I was completely clueless as to what they were talking
about).
> With decades behind, I have a clue about one workstation being oh so
> powerful and about server farms doing rendering, 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...

As Chet mentioned, NeXTs ran NeXTStep, which was based on Mach and 4.3-ish
BSD. My sense was that they were underpowered and overpriced for the time;
they were 68k based in an era where RISC processors were dominant (or
becoming dominant) on the high end and they cost something like twice or
more that of a contemporary Macintosh while targeting roughly the same
userbase.

The software was really the interesting thing on NeXT machines. Oh the
hardware was nice enough, don't get me wrong, but compared to a SPARC or
MIPS-based workstation, I'd choose the latter every time. However, NeXTStep
was not very "Unix-y" if you were used to BSD or even System V Unixes of
the time. Things as basic as the directory structure were weirdly foreign
(though will look familiar to users of macOS now), and it used "netinfo",
which was a distributed directory service they'd built, rather than NIS or
anything remotely interoperable with the rest of the world. But the
NeXTStep user interface was very nice, and Display PostScript was
beautiful. The Objective-C foundation classes were very powerful. But it
was clear that you were meant to interact with it through the GUI, and
CLI-style interaction was an almost totally separate universe (or so it
seemed to me at the time).

One got the sense that NeXT was targeting users who had sort of outgrown
the Macintosh, but weren't ready to make the leap to a full-on workstation
on the low-end, and simultaneously trying to bring users from high-end
machines into a totally new ecosystem. But that was a really small market
and application vendors didn't jump on board: the Unix applications weren't
there, and neither were the standards from the Mac world. A few things got
ported, and that was cool, but perhaps sadly, Jobs just couldn't pull off
the magic twice, and NeXT failed. Much of the technology lives on in
macOS, though.

There's a great book about it, "Steve Jobs and the NeXT Big Thing" that's
worth a read.

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 3338 bytes --]

  parent reply	other threads:[~2023-01-27 15:55 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
2023-01-27 14:49                       ` Ron Natalie
2023-01-27 15:53                     ` Dan Cross [this message]
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=CAEoi9W7WyNDHLmr5BqLxyK3sQSX0VTU6FZG32z5n20O6iAzx8Q@mail.gmail.com \
    --to=crossd@gmail.com \
    --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).