BeOS was also optimized (probably over-optimized) for first impressions; the immaturity and architectural mistakes were hidden behind a facade of "OMG it's so fast and pretty". The BeOS GUI with its cartoony 32x32 icons was also a lot closer to MacOS than NeXTSTEP with it's huge high-DPI GUI, so BeOS looked like "Mac done right" while NeXT was a foreign culture.
So yeah, NeXT was better but most Mac users had no way of knowing that at the time.
However, BeOS was far more stable/mature than its 'developer release' status implied. I remember how blown away people were at the dev release in 1996 by how solid it was, not just by how forward thinking its features were.
I don't think multiuser would have been a showstopper for release if BeOS was acquired by Apple. They could have put out 2-3 versions of a single user OS and few would have cared.
But Be, Inc. and BeOS really strike me as the kind of design, company, compromises, focus and leadership/team that I've come to associate with startups that are actually designed to be acquired by the executive's former employer after some time.
I would love to know if this is true, though in my experience, that is usually only known to the founders and executives except in the really obvious cases.
[1]https://en.wikipedia.org/wiki/Jean-Louis_Gassée
[2] https://mondaynote.com/50-years-in-tech-part-11-getting-the-...
This is very common for "startups" founded by executives who come from a company they know is failing to execute on something critical.
Be smells like this.
Or by “someone else”, did you mean someone other than PalmSource?
Let’s be honest, though: most new OSes don’t enjoy much success or longevity. The only successful new arrival I can remember recently was Android, and it had the backing of Google, and was aimed at a relatively new market. It also borrowed heavily from established tech: Linux kernel, JDK and JVM.
I doubt there’s more than a handful companies that could have turned BeOS into something big, and of those, Apple was probably their best bet.
* BeOS was evaluated by Apple as a Copland replacement (along with Solaris, NT, and NeXTSTEP).
* MacOS X discarded DPS for Quartz so it didn't turn out to be much of a feature. But very few applications touched that directly so it wasn't much of a porting issue.
* There was more UNIX and AppKit-based software available for NeXTSTEP than for BeOS but nobody in the Mac world cared about that. Quark were the only company that really blew the transition, but they blew it badly.
I think a lot of people start mashing years together when it comes to BeOS. Apple announced the NeXT acquisition in December 1996.
In December 1996, BeOS was still a developer preview with the first "real" release still about two years away. NeXTStep was already 8 years old.
In 1996 BeOS was at a completely different state of readiness and maturity than it was with R5 (which everyone remembers fondly).
USENET is full of posts, 96-98, of individual developers announcing with triumph the porting of UNIX core utilities to the BeOS developer release versions-- utilities that were already present and mature in NeXT/Openstep.
Mac OS X Server 1.0 was released about two years after the deal was finalized and I imagine it would have taken about two years of really hard work just to make BeOS multiuser, nevermind porting all of the core utilities.
It took a couple more years (it was a somewhat jerky transition for many users) before a "usable" OS X was released but from the beginning there was an wide variety of software available for it that was easily ported from NS/OS, and features like Display Postscript, Objective-C, a mature set of APIs, and most importantly of all Project Builder were there from the beginning.
The software scene on BeOS in 1996 was... sparse.