back
104 comments
I was lucky enough to have a friend working at BeOS at the very end. This is when they abandoned all hope of getting bought by Apple (erm... I mean gaining presence on the desktop) and focused on "Internet Appliances" like eVilla.

BeOS was really amazing at the time, especially in comparison to 'next generation OSes' like Windows NT, the vaporware that was Copland, Linux (which was unusable for mortals) or Solaris. It was clear to me that the future was going to look like BeOS or NeXT, but I could actually easily download and run BeOS on my mac. It was incredibly useable... I installed it and was able to use it for months. It just needed apps.

When Apple went with Jobs (and thus NeXT) I thought that made sense. But when I saw the early releases of Rhapsody I really thought they had made a huge mistake. BeOS was just so much better.

It's really fun to fantasize about what the world would have been like if BeOS made it big. There's still a lot of tech there that has not yet made it into desktop OSes.

There has yet to be a better technology to win in the desktop OS.

Examples 1) CPM was so much better than DOS

2) Amiga was 7 years ahead of its time (Though the OS had a ton of bugs the first 18 months)

3) BeOS

4) We still deal with a corporate IT that is 90% Window shops for corporate desktops. (Though Windows has gotten MUCH better)

5) Gnome and GTK+ gained more mind share than KDE :) Okay that one is personal opinion but :)

Gassee really overplayed his hand.

Had he been more reasonable, Apple would have acquired Be Inc and based their next generation OS on BeOS.

I had a similar feeling when I tried Rhapsody DR1. Yeah, it was kind of cool and had potential but Be had a real working OS that was just waiting for that Apple polish.

In the end, Jobs and his vision were probably better for the long term health of Apple but at the time, I too thought that Apple was making a mistake.

I still like to muse about what could have been.

BeOS was great, but compare Steve Jobs' NeXT presentation (1992) to the BeOS video: https://www.youtube.com/watch?v=gveTy4EmNyk

NeXTSTEP is the predecessor of OS X, the rest is history.

BeOS filesystem "BeFS" had extended attributes (metadata) with indexing and querying features similar to a relational database and Bill Gates' vision of "information at your fingertips". Though Microsoft failed to complete Cairo-OS as well as WinFS. The BeFS main developer wrote a book about it, as it is out of print now he released it as PDF for free: http://www.nobius.org/~dbg/practical-file-system-design.pdf , http://en.wikipedia.org/wiki/Be_File_System

Check out HaikuOS, an open source BeOS reimplementation: http://en.wikipedia.org/wiki/Haiku_(operating_system) . And there were two BeOS inspired OS: ZETA-OS and SkyOS with some shady history: http://en.wikipedia.org/wiki/Magnussoft_ZETA , http://en.wikipedia.org/wiki/SkyOS

Some of the BeOS vs. NeXTSTEP history is documented in Apple Copland OS article: http://en.wikipedia.org/wiki/Copland_(operating_system)#Canc...

Another interesting video is: https://www.youtube.com/watch?v=UGhfB-NICzg (In 1991 Steve Jobs' company commissioned an head-to-head programming competition to show how much faster and easier it was to program a NeXT computer vs a Sun workstation. The NeXT operating system went on to be the foundation for Apple's Macintosh OS-X about a decade later.)

What was amazing was all of what BeOS could accomplish on almost exactly the same hardware Apple was shipping. Pretty extraordinary accomplishment at the time. There are some technologies in NeXT which are invaluable today e.g. the native PS/PDF support and UNIX underpinnings but I think BeOS would've delivered far more bang for the buck in the short to medium term. I agree it's great to look back and wonder what if.

One technology that always gets forgotten in this saga was WebObjects. Had Apple actually released it for free it could've been the standard for all web applications built during that time. Absolutely nothing came remotely close to it. Instead it went on to inspire technologies like Hibernate and JSP/JSF which dominated early web applications.

Of the two, I found NeXTSTEP / OpenStep easier to program and a lot more feature rich. BeOS felt like it had better performance, but was harder to program and didn't really have the development tools.

In retrospect, it was good thing Apple bought NeXT, but they sure lost a lot of cool things in the transition to OS X. BeOS seemed like the OS that could have still competed if they had skipped "Internet Appliances" and gone for the sub $500 market. They could be performant on low-end hardware.

For anyone who is prone to ignore vertical dynamics, keep in mind that this OS was competing with Mac OS 8, Windows 98, and GNU/Linux in the Lesstif/GNOME 1.x era. In short, it trumped all the rest in speed, development environment, multimedia, stability...

But the Wintel cartel was stronger than ever. Microsoft even settled with Be years afterwards for colluding to keep their OS off of any vendor computers. But that can't ever commit backwards into history what computing would be like if the best OS at the time had been given a fair shake.

Was just chatting with someone about my feelings toward the "new" Microsoft. I admitted that, no matter what moves they'd make, I just wouldn't care, as I really can't forgive them as a company for all of the shitty, anti-progress moves they made. Embrace-and-extend anyone?

Thanks for the reminder (that I had forgotten about) of just one of the many actions they took that makes me wish corporate capitol punishment had been an option.

If I were BillG I'd be trying to philanthropize my heart out too.

I cant understand why more people dont realize US is not a capitalist or free market economy.

Or even the EU.

If you look closer at any industry you'll see cartels, monopolies, government support and skeweing what and who gets the money. Who gets payed and who doesnt. The best products do not win, the best companies do not win.

It seems the different vs USSR is the scale of the economy.

Both KDE and Gnome were actually in their 0.x's when the first non-preview BeOS was released, and BeOS had been kicking asses long before these projects were even started. It was also kicking asses in the era of Mac OS 7 and Windows 95. Although at the time, I think it was pretty much limited to the BeBox (which in itself was an amazing machine).
What would have been the plausible avenue via which it could have taken off, even if Microsoft didn't take interest? There was no software, and the only connection to outside software world was the POSIX API supported for text-only apps.

Their aim was to be acquired by Apple and get the throne that OS X now occupies, and after missing that chance they were left a niche hobbyist OS for Amiga refugees looking for a new technically superior underdog to root for.

It was given a 2nd opportunity, but its owner was too greedy.
Even without MS push, it may not have been a different story. BeOS was to generic, without any niche. Without MS Office etc it would have been difficult to capture any market. Linux was successful as a free UNIX clone, so instead of paying 1000s of dollars to sun, IBM you could have a free UNIX with a good webserver with PHP Java and all. BeOs never had such a ready market nor a niche.
I remember installing BeOS a long time ago, when I was fiddling with old linux distros which were almost impossible to install (what is the model of your RAMDAC? which is your interrupt controller? manually configure your modem!)

I was absolutely amazed at the ease of install, running the software and the powerful GUI. I even ran it for some months as my only OS, since it had a web browser and e-mail client and the dialup config was very straightforward.

After that time, I started missing a lot of software, especially browser updates, so I tried linux again and found that it had improved a bit, so I stuck with it.

But I'll never forget how probably the best OS at that time failed into misery for the lack of software and a bit of promotion.

Hey carlesfe, see my previous post -- it was not a simple lack of promotion but a complete lockout from pre-installation for any PC vendor who didn't want to get royally stomped on by Microsoft.
I remember Debian asking these questions for years after PCI was mainstream ( PCI has device IDs that Red Hat would simply look up in the PCI map file to get the proper kernel module).
In early 2008, having graduated from college the year before, I was living in the midwest working at a company making warehouse management software. I decided I really wanted to work at Be. I sent them my resume for a position that was posted (I think I actually snail mailed it). I called the recruiter and she politely informed me that I wasn't qualified for it. Shortly after, I saw another position posted and applied again. Over the next 7 months, I continued to bug the recruiter regularly until someone finally broke down and gave me an interview. I bought a new suit just for it. When I showed up to interview, an engineer walked in with long hair and ripped up jeans.

I ended up getting the job and worked there through the end of 2000. Even though it ended up imploding, it was a great experience. I learned an incredible amount and I'm still friends with a bunch of people I met there. Many of the people from Be ended up at Android.

I think you must mean 1998, not 2008?

This is a good story. I'd be curious to hear about things you learned that are related to unusual aspects of what Be was doing.

I found my BeOS install CD and floppy the other day.

I never really had hardware that could really use something like BeOS back then.

If you liked this then you should consider supporting the Haiku project. They are keeping BeOS alive.

https://www.haiku-os.org/

I'm wondering though if anyone here can speak to how much C++ was used in writing the kernel? I've heard multiple stories...some say that all of it was very OO, some say it was C with classes kind of stuff.

If you like BeOS, you should check out Haiku which is an open-source OS inspired by BeOS [0].

[0] https://www.haiku-os.org/

It's a good project; thankfully there is still the BeOS book within it so you can write applications on it using the tidy BeOS API. I think there are GCC 2 and GCC 4 compatibility issues (attempting to maintain binary compatibility won't work with GCC 4), and they have got a package management system which some feel was too Linux-like, but it's an interesting project and can breathe life into an old computer somewhere.

Speedy too!

I ran BeOS for almost a year around that time. I remember it as fairly stable and packed with neat little features that made it feel lean and modern. Then I started to get disappointed that the community didn't seem to be growing fast enough... It felt a bit like computing while stranded on a desert island
I was tripple-booting Linux, Win2k, QNX, and often booting the BeOS demo from floppy.

The BeOS driver for my 3c905 Ethernet card was buggy and about every other morning I'd wake up to find a dialog to the effect of "Your network driver has crashed. Click OK to restart the driver." It stunk to have a poor driver, but it was really cool that a bad driver didn't take down the system. A couple years later, I had a CD-R with some of my old financial records on it that got corrupted and would kernel panic Linux, Win2k, and OS X. These days, DVD and CD drivers should really be in user space.

Though, I was playing around with semaphores and found a way to reliably kernel panic BeOS, though the exact same source ran perfectly on Linux. Enough kernel panics and I slowly got filesystem corruption. One morning I woke up to my disk light being on. It spun all night and wore a visible track into the coating of that floppy. Both the floppy drive and the floppy were ruined. I used the vendor's version of tar to back up my data before reinstalling the OS. That's when I learned that all of the NetPositive browser bookmarks were stored as zero-sized files with the links in metadata that wasn't preserved by tar. When resizing the partition once, I learned that non-tar-preserved metadata was also what kept the userspace drivers from showing up in the BeOS task bar.

As much as it would have been cool to have OS X based on BeOS, QNX was much lighter weight and robust. Plus, the QNX Photon GUI subsystem was like X11 and Synergy on steroids. OS X is a lot of things, but the Xnu kernel is quite heavy, and it's not clear that it's possible to implement Mach ports in a lightweight manner. Both BeOS and QNX show it's possible to have a light weight high performance kernel that's isolated from most driver bugs.

This video always makes me wish Apple would have bought Be, Inc. instead of NeXT. The BeOS was much more interesting than NeXTSTEP!
It'd be interesting to know where Apple would be if they had bought Be, Inc. Would we have iOS? Would Apple be successful? All very interesting!
A lot of the android architecture is inspired by beos... Iirc Especially the stuff around intent-based IPC.

Two key android devs, romain guy and Dianne hackborn, were on beos.

Ah the nostalgia. In 1999 I was a sophomore in college and built my first PC that was all my own. I used the legendary Abit BP6 Motherboard http://en.wikipedia.org/wiki/ABIT_BP6 I had a pair of Socket 370 Celeron 366a processors overclocked to 100mhz, which made the system think it had a pair of P3 550mhz cpus.

BeOS was a great OS for experimenting SMP. The CPU monitor in the video would show you the loads for each CPU and you could click the left side to toggle a CPU on and off. You could immediately see frame rates drop and the remaining cpu's usage spike.

Similar story. I put together a dual-P2/350s on (I think) a Tyan motherboard in December 1998 as a dedicated BeOS host. Wasn't good at budgeting and found myself in another state having run out of money a few weeks later, and had a bit of a challenge getting home.

Parts of haiku remain impressive. Example, there's two performant message-bus mechanisms available via standard system calls:

* The flagship IPC mechanism is the BMessage. You can exchange messages unicast, or broadcast using BRosterm, or pub/sub with StartWatching/SendNotices.

* You can also treat the filesystem as an async messaging system using BPathMonitor. Yes, you can create RAM disks. They have FUSE as well.

It runs pretty well under VirtualPC. There's a trick to configuring the mouse to touchscreen once you've installed the seamless-mouse tools.

Crazy, I have almost the exact same story and the exact same setup. I replaced a new 400mhz Pentium 2 setup with that Abit BP6 board and ran the 366mhz processors at 466mhz or 533mhz when it was cool out (I opened the window to help cool my system). Probably wasn't the greatest investment, since the 400mhz Pentium 2 was still a really nice processor when I did this (early 1999, I believe, towards the end of my freshman year of college).

I ran multiple OSs: BeOS and Redhat Linux to do my CompSci work for school and then Win98 (which only supported one processor, of course) to play games, mainly Quake 2 and Tribes.

I had an original BeBox, which I upgraded to the faster CPUs when available. I bought the BeOS team a case of champagne when they shipped a major release.

I'm happy Apple bought NeXT.

Out of interest, why are you happy that Apple bought NeXT instead of Be?
I've still got my BeBox and boot it every year just to confirm it still works. It still works! I have no clue what I'll do with it - its not worth selling. Anyone got any clues?
Ah this brings back memories! I happened to go to the Be developer conference back in summer 1996 - didn't know anyone, wasn't even a developer, just a curious high schooler interning at a mac user group down in LA. Hopped on an airplane alone to come out to San Jose because why not?

I remember talking to some Apple exec sitting next to me in the presentation room as some Be people finished their speech. I asked about their prospects and he said something like 'yeah its been tough for us but Gil Amelio is going to turn things around'. Gil had just joined as CEO back in February. I remember thinking that the guy didn't sound like he really believed what he was saying though - there was a a certain resignation, or just a moment where he didn't feel he had to keep the 'everythings great' performance up for a high school kid. After the NeXT acquisition I remember thinking about this guy and that he probably didn't have a job anymore. Who knows, maybe that was actually Jonny Ive.

At the conference there was a whole group of Apple people checking things out and talking to everyone. I don't remember if it was public knowledge that they were negotiating with Be at the time, but it was no secret why they were there. There was a lot of excitement among the developers there, but also a lot of trepidation - there was just loose talk of being useful for really specialized AV fields but no path or believable / clear idea of how this could go to mass market. Even a 15 year old knew that. Plus, Microsoft was unstoppable back then. A fair amount of talk among the devs was about how this could be the next Apple OS, and I think that's what excited people. But everything hinged on acquisition.

Afterwards I think I exchanged a few emails with Dominic, because I was interested in BeFS. I didn't really know how to talk to him so I think I just offered him access to my mp3 server. Meanwhile when I got back to the mac user group, I installed the developer preview CD on some PowerComputing macs we had and they just transformed into beasts. BeOS was otherworldly, using it felt like you were 5 years in the future but in an alternative universe (full of tiny yellow title bars). Because all of the apps were just apps to show off Be's capabilities, it was also vaguely reminiscent of the 90s demoscene, with Be one-upping Future Crew by dropping an entire OS.

History shows NeXT was the right move. But Be... they were something special.

OMG brings back memories and makes me sad at same time it failed to gain ground. I was a BIG BeOS fan. In fact I'd probably be able to dig up from my storage the actual purchased BeOS package and the "The BeOS Bible" book I bought too. It was the "Opera Browser" of operating systems at the time to me. Lightweight, nimble, fast and just completely felt it was well thought out by brilliant engineers that weren't tied down to legacy.

I remember pitching it to my co-workers and praising its ability to still play multiple movies smoothly in a dragging window even with other tasks running in the background, which at the time was really cool considering same hardware Windows/Linux could not. And to this day, it had my favorite all-time newsreader (can't remember the name but it was threaded news that used multiple windows)

In the end, it just didn't the apps and the world was Microsoft centric and this thing called "Linux" was the buzz, along with Apple gaining ground.

Wow, I haven't seen this video in a long time.

Buying a BeBox was one of the best things I ever did. I took out a loan for about $2,000 from my bank to get one and start writing apps. Not a lot materialized out of it financially but the experience was invaluable. I met a lot of people from the community that I still chat with to this day.

Be, Inc had some really good ideas.

Still got your BeBox? I turn mine on every now and then to make sure it still works - I don't think I can ever bring myself to sell it, but I'm still at a loss as to what I will do with it.
I owned a dual 66mhz back a few years ago. Hands down the coolest piece of computing hardware I've ever purchased. I regret selling it at least once a month. I will never find another one.

It still blows my mind how good the OS was. Could deadlock the entire system, but I'll be damned if your CD was going to stop playing perfectly. Not even a skip.

BeOS is a good example why if you're already big you can be proprietary but if you're small it's better to release as open source (when there are big players in the market.)

If BeOS had simply released its source early on it might still be very much alive and healthy today. Given that it achieved on the desktop what Linux still has not, it might have bested Linux in at least the desktop arena. It's main mistake was trying to make it in the proprietary OS market, up against both Microsoft and Apple. Certainly after Apple had failed to buy BeOS, their next best bet was transform BeOS into a GPL or BSD-licensed project.

Now, we have Haiku OS, but it is a bit late, and can only ever be an approximation of the original experience / API.

When I was a kid I was running BeOS and it was really cool at the time.
I remember being impressed that the BeOS media player could play audio CDs backwards in real-time. Not really sure why you'd want to but it was quite a good party trick.
yeah, could transcode anything to anything in real time and feed it to an appropriate player.

BeOS is the only OS which implemented the same UX of unix pipes in a way that actually made sense in a graphical environment.

Is it time yet for a new OS that emphasizes immutability, security, concurrency and other functional-language paradigms?

I feel like even today, we are not seeing the true possible performance of our hardware due to all the "sediment layers" (as Jean-Louis Gassée put it) of our popular OS'es. We're also not seeing the possible reliability and security, either.

MirageOS? (http://openmirage.org/)

I kid, but only a little.

I feel the same watching this or Shawshank redemption. There's some lost beauty in it. Even BeOS source code / API was beautiful. I remember some code to query and filter FS results based on metadata, not far from a tiny SQL C++ eDSL.
At 13:00 he demonstrates positional audio. Whoever uploaded this to Youtube reversed the channels so the sound pans right when he moves the source to the left.

Twenty years later and why doesn't my computer come with a 3D mixer already?

Running BeOS on my Pentium II Celeron 333 MHz was pure joy. It's such a shame it didn't amount to more than it did.

That and OS/2.

This is the perfect example as to why we need to focus on the customer problem not the technical solution.
I remember that. I also remember all the excitement around it and then it fizzled.
Are current Linux distributions as good as this yet?