Slashdot Mirror
History and Perspective on BeOS
prepp writes "Avid BeOS user Robert Renling posts his first article
about the Be Operating System." An interesting little article, with the amusing conclusion that BeOS isn't dead after all! Ah Zealots. Aren't we fun?
They boot from the CD like you'd expect any modern OS to, and they come with a hacked up ver of LILO called BELO:)
I do agree about the Ross Perot thing though: it made a few people wake up to features they could provide and raised the bar for speed and responsiveness, but just like with Perot, as soon as Be became a non-issue the OS vendors relaxed and continued as before.
OpenBeos
Blue Eyed OS (B.E.O.S)
YellowTab
and BeBits gets updated regulary with new applications for the BeOS.
the BeOS is down, but not out...the Be community is still very strong!
--- Brad (http://www.LinuxReview.net)
So, on the one hand -- yeah, if the source and tools exist, and if there's enough of a userbase to profit by providing that support, an old application and/or operating environment can survive long after the original vendor bites the dust. But this is a small minority of all the systems that have lived. So you shouldn't expect something like BeOS to last much longer given lack of source and the small business community which invested in the environment. Hell, how long will it be before VMS joins the crowd of relics I listed previously?
Your point about vertical applications is valid, though I given that BeOS is a commodity no different than WinXP, MacOS X, Linux, or any other operating system a vendor targeting vertical markets like you list would provide their customers with a better solution by choosing widely deployed platforms. I honestly think they would be doing a disservice to their customers to recommend BeOS given that it lacks any kind of corporate or large community developer base, never mind original source.
Cheers,
--Maynard
I ran BeOS starting with the early developer release, through PR1 and 2, up through Person Edition 5. BeOS convinced me to buy a Power Mac clone, and once they transitioned to Intel, to buy Intel hardware.
One thing missing from the above discussion is one of Jean Louis Gassee's original design goals for the BeOS: symmetric multiprocessing. During the early BeOS days he would frequently repeat "one processor per person is not enough." That's what convinced them to build their early AT&T Hobbit-based multiprocessor machines, and eventually the BeBox, the dual PowerPC machine designed by Joe Palmer and beloved by many hackers. They did it because there was no cheap multiprocessor hardware available at that time. The goal, said JLG, was a multiprocessor machine that you could "lift with your credit card."
But JLG was wrong. He thought that people would have a never-ending desire for more processing speed, and that the right way to meet that need was to build computers with multiple CPUs at the price-performance sweet spot. And in 1990 that seemed true. But through the 90's CPU speeds increased to the point that word processing, e-mail, Internet access, and 2D graphics editing became fast enough for ordinary use on even the cheapest hardware. Suddenly there was little benefit to an intentionally-not-backwards-compatible OS.
Doing symmetric multiprocessing (SMP) well is difficult. To do it right requires a lot of thought about which parts of the system can be threaded and how to avoid threads locking on shared resources. Be's solution to this problem was to rewrite the whole system from scratch -- from the kernel to the filesystem to the GUI. And they didn't care about backwards compatibility; it always seemed like the POSIX layer was an afterthought (remember how many versions were released that didn't support select()? )
So once the performance benefit of BeOS (at least for most desktop users) vanished, what was left? Little hardware support, given their small development team and no vendor support. A not-particularly innovative GUI, since they decided to closely follow the predominant Windows/MacOS design. A beautifully designed API and highly modular system, but unfortunately not one that had any end user benefits.
It's ironic to think about what would have happened if Apple had purchased Be. True, they would have lost Steve Jobs, and perhaps the company. But a MacOS X-class OS would have shipped four years earlier, and had outstanding multiprocessor support in the core. Apple didn't bite, Be had nothing left, so they died. Sad.
While we did stop making it, we never stopped supporting it. I remember doing installs and testing of 5.0 (the last release) on BeBoxen.
They abandoned the Mac users that ran BeOS on Macs.
Not our fault, Apple's fault. Apple refused to release the specs for the G4, and we didn't have the resources to reverse engineer it. We kept supporting PPC 601-604 Macs until the end.
They abandoned BeOS users and developers to pursue the (idiotic) network appliance market
That was a last ditch effort to survive. We were losing $20 million a year on $2 million revenue selling BeOS to the desktop, with no prospects for improvement in the year we had left before running out of cash.
Not surprisingly, the network appliance makers were not eager to jump into bed with a company that might abandon them next.
Perhaps, but several (including Compaq) did sign on to use BeIA, only to switch to WinCE under threats from microsoft.
A legparnasom tele van angolnaval.