Be, while an innovative OS in its day for sure, is more interesting to me as a business story. Most people don't realize how close BeOS came to becoming Mac OS X. They had the inside track on the deal, and their OS was technically superior to Next's. But Gassée's determination to hold out for more money combined with the famous Steve Jobs reality distortion field to consign Be to the dustbin of history and cleared the way for Jobs's second coming at Apple. How different the tech world would be today if Gassée had said yes to Apple's initial acquisition offer. I wonder how often he thinks about the breakdown of that deal, lo these many years later.
There were definitely some egos involved. According to some accounts I've read, Gassee was forced out of Apple due to disagreements with Sculley. I worked at Be and spoke with Gassee, so I know he's kind of, um, "volatile," let's say. He probably felt ill-treated at Apple and this was his chance to right a previous wrong.
BUT. I used and developed for BeOS for many years. And now I've used and developed for MacOSX for many years. And I think Apple made the right decision, both technically and politically.
At the time, NextStep was far more mature. Next was a lot better funded than Be was. And Apple's original DNA was formed in Jobs' image, so he was far better prepared to run the place.
IIRC, Be was not technically superior. It was a one-user no-security pre-internet OS which had been highly polished in for one task: concurrent multimedia. It would have require a lot of work to bring up to scratch as a graphical design platform to rival NeXT (which was always about ultra-precision, and even used PostScript to draw its GUI).
This is very true. I like to think that, in a lot of ways, Be was what Mac OS 8 (the original Mac OS 8) should have been: a massive, massive improvement on the design of System 7, while retaining the general feel of the operating system. NEXTSTEP and OPENSTEP were always more about being a vast improvement on Unix. Yes, Be had some POSIX emulation, but there's a huge difference between that, and actually integrating properly with a complex multiuser Unix network with shared directories, site-wide logins, and so on--something that NEXTSTEP had had time to hone to perfection due to its heavy use in academia and government.
BeOS is still interesting to me, but mostly in a historical sense. I have to agree that purchasing NeXT was a vastly wiser decision.
EDIT: As a quick addendum to my post: although this has changed in the intervening years, the one thing that Be definitely did have going for it back then was that its kernel was technically superior, delivering mostly the same benefits of a true microkernel design, but with vastly superior performance to Mach. I have no idea what the current state of things would be on that front; between Apple merging BSD into the kernel space and replacing DriverKit (Objective-C) with IOKit (eC++), the differences are probably minimal.
That is possible. It is also possible that Apple would have thrived in different ways. There would likely be no iPod and no iPhone. Jobs would likely not be the legend that he is today, though of course he would still be in the history books. What is certain, though, is that Be, as both a business and a technology, and Gassée as an individual, are exponentially less successful now (by standard business metrics, not necessarily in a deeper sense) than they would have been had Gassée said yes. I wonder if that still haunts him, or if he has made peace with it.
There wouldn't have been an iPhone, but the Newton would most likely have become a smartphone platform.
(Actually a hypothetical 2002 NewtonPhone might have been quite the killer product against the first iterations of Symbian, Windows Mobile and PalmOS on Treos...)
No, Jobs didn't invent digital audio players, nor did anyone else at Apple. But Jobs decided to pursue it as a business. The story -- apocryphal or no -- is that Jobs named Apple Computer after the Beatles' label, Apple Records. He has always been a music fanatic. It is unlikely that with anyone else at the helm Apple would have driven as hard or as far into the music business.
I don't think technical superiority is as clear cut as that. From memory BeOS was better in some areas, and NeXT in others. I'll go find out which was better where and why.
I think things would've been very different if Be Inc. had just kept being a desktop OS company. They didn't need Apple to succeed -- they could've just accepted that uptake of the OS would be slow, and just kept at it.
Guess that wasn't good enough for management though. They had to go out in a blaze of "Internet Appliance" glory.
Just like TFA I booted Haiku in VirtualBox... Several years ago I ran the BeOS R5 livedisk, and while this is reminiscent, since I'm running in a virtual environment it falls short.
Running BeOS on the metal was amazing - setting a thread to realtime would make it really snappy, and it's just not the same when it's virtualized...
Either that or Haiku has some way to go yet - I can't tell...
EDIT: you know what? actually, this is still really impressive... it DOES behave a lot like BeOS, and it's alpha... I crashed firefox, and gdb popped right up. I dropped into a shell (bash) and there was a GNU style environment right there. That's actually really cool!
Long ago, I was a beta tester and ran BeOS on a dual ppro 180, for a time, and it was lots of fun, turning processors on and off and bouncing balls between windows. I wish more companies would be as visionary and innovative as Be was, and give us some new, different computing platforms.
I remember installing BeOS when it came out. It was impressive and beautiful, and I really wanted it to catch on. I think I'll give Haiku a spin. With VMware, it'll be much easier this time around.
Not really. Most of the core devs run it on bare metal. So far, I've tried it on my custom built PC, a Dell Inspiron and a Toshiba Satellite. Works perfectly.
What if host systems evolved to become little more than virtual machine managers, dealing with hardware drivers and so forth - while the user-space operating system is freed from having to worry about the actual hardware being used unless it really wants to?
I don't really care about the BeOS / Haiku kernel. We could use Linux for all the h/w support there is. BeOS was impressive but I guess Linux can be made to play a dozen videos at the same time, too. And I usually stick with only one.
But the user space and the user interface are brilliant!
I would trade Gnome, KDE, Windows, OS X, or $NAMEIT for the BeOS userland any day, both as an end-user (wrt. UI) and as a developer (user-space API). I hope we'll have more choice in the future.
How about this: install Debian, 'apt-get install kvm' (okay, you'll probably have to run that through module-assistant, but still, it's only a few more presses of 'Enter' away), then run 'qemu-system-x86_64 haiku.img -m 2048'. Voila! Linux as hardware abstraction layer and virtualization engine, with Haiku running on top.
Man, I remember how badly I wanted a BeBox when they first came out, partly because the hardware was a hobbyist's paradise (a Geek Port, for chrissake), and partly because the UI was so pretty.
But, Linux and MacOS have come pretty far in the intervening 12 years, and without any special hardware to go with it, I just can't muster the excitement to mess around with Haiku.
It sure is an impressive piece of software. I hope it catches on, or find itself a niche market.
I wonder if they're doing anything for developers to easily leverage pervasive multithreading, the bare bones fine-grained threading can be a pain to deal with.
Geez. All this Be nostalgia lately has had _me_ pining for it, and I've never used it. Gonna try out R5 on my old pentium II. Hopefully it'll replace XP. It seems fitting, as that computer is nothing more than a toy for making art.
