From: "Charles H Sauer (he/him)" <sauer@technologists.com>
To: tuhs@tuhs.org
Subject: [TUHS] NEXTSTEP 486 [was Re: Setting up an X Development Environment for Mac OS
Date: Fri, 27 Jan 2023 10:12:38 -0600 [thread overview]
Message-ID: <d9517190-265c-99ca-75bc-20087a3fa6d4@technologists.com> (raw)
In-Reply-To: <CAEoi9W7WyNDHLmr5BqLxyK3sQSX0VTU6FZG32z5n20O6iAzx8Q@mail.gmail.com>
NEXTSTEP was (is?) interesting for many reasons IMO, especially what
Berners-Lee did at CERN, and can still run today on appropriate 486
machines.
I was in the thick of getting NEXTSTEP on 486. See
https://notes.technologists.com/notes/2019/07/01/koko-exploring-nextstep-486/
and
https://notes.technologists.com/notes/2019/07/01/koko-reviving-timbls-worldwideweb-browser/
Though our JAWS machine was Jobs' preferred demo machine for NEXTSTEP
486, NEXT supported a surprising variety of machines and peripherals by
the 3.3 release. I have NEXTSTEP 486 (and other old OS) running on a
couple of more popular Dell 486 machines as well as JAWS
(https://notes.technologists.com/notes/2019/09/26/koko-welcome-to-eight-jurassic-o-s-on-1992-dell-486d-50/).
There are probably many other early 90s 486 machines that could be made
to run NEXTSTEP 486.
Charlie
On 1/27/2023 9:53 AM, Dan Cross wrote:
> On Thu, Jan 26, 2023 at 11:08 PM Will Senn <will.senn@gmail.com
> <mailto: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.
>
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com
fax: +1.512.346.5240 Web: https://technologists.com/sauer/
Facebook/Google/LinkedIn/Twitter: CharlesHSauer
next prev parent reply other threads:[~2023-01-27 16:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:38 [TUHS] " 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
2023-01-27 16:12 ` Charles H Sauer (he/him) [this message]
2023-01-27 14:17 ` 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
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=d9517190-265c-99ca-75bc-20087a3fa6d4@technologists.com \
--to=sauer@technologists.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).