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?

280 comments

  1. BeOS by joyoflinux · · Score: 3, Funny

    BeOS may not be dead, but everyone tells me BSD is ;-)

    1. Re:BeOS by morgajel · · Score: 3, Interesting

      it's really great when they tell you it while holding an ibook:)

      but now on to the topic- BeOS was my first alternate OS. I went from 98 to BeOS 4.52
      it rocked. the only problem it had was with my video card, so I had to keep switching in an older one to get it to work. That was also the reason I finally quit using it. If you want to know more about the BeOS, I'd highly recommend reading the BeOS Bible. It was a very well written book for someone who(at the time) didn't know much aobut computers.

      --
      Looking for Book Reviews? Check out Literary Escapism.
    2. Re:BeOS by Raiford · · Score: 1
      That was actually kind of funny -> mod parent up

      --
      "player 4 hit player 1 with 0 stroms"
    3. Re:BeOS by flikx · · Score: 3, Funny

      You don't have to be a Kreskin to know that BeOS is dying...

      Aw screw it. It's hardly even worth it anymore. :)

      --
      One future, two choices. Oppose them or let them destroy us.
    4. Re:BeOS by rice_burners_suck · · Score: 2

      I dunno, man. It looks to me like BSD is alive and well, and doing better each day. As a matter of fact, back in the BeOS days (since R3, when I bought my first BeOS CD, and up until the dot com crash), I used FreeBSD and SuSE Linux for all my serious stuff, and ran much of my desktop stuff on BeOS. When Be, Inc. turned to poop, I blew BeOS off my desktops and installed FreeBSD with XFree instead. As a matter of fact, I doubt I still have Linux installed anywhere, as I became so happy with the well-structured FreeBSD filesystem that I blew Linux off as well. And I must've updated FreeBSD about 4 times since those days. So if anything is dead, it's not BSD, that's for sure.

    5. Re:BeOS by Anonymous Coward · · Score: 0

      I guess you don't have a sense of humor...

    6. Re:BeOS by Anonymous Coward · · Score: 0

      Ah, so as long you are using BSD, it will never die? That must mean BeOS isn't dead either, as afaik lots of people still use it.

    7. Re:BeOS by Howie · · Score: 1

      it's really great when they tell you it while holding an ibook:)

      Because that makes them look like they're saying it with an inexpensive laptop in their hands? I don't get it.

      OS X isn't BSD, as the entire OS X userbase seems to pop up and say whenever the BSD-is-dead thread starts up again. It's a microkernel with a BSD-like API over the top (or something like that).

      --
      "don't fall into the fallacy of believing that Perl can solve social problems. Maybe Perl 6 can, but that's a ways off"
    8. Re:BeOS by Anonymous Coward · · Score: 0

      It's nice, everyone tells you BSD is dead, but an
      OS which has still Brands being actually developed on, is definitely _not_ dead at all.

    9. Re:BeOS by zonker · · Score: 0

      well i've heard plenty of beos zealots ask "why didn't apple use beos instead of next", so i would guess a few are probably from that camp... ;)

    10. Re:BeOS by Art+Tatum · · Score: 1
      OS X isn't BSD

      True enough. OS X is OPENSTEP/Mach. :-) As the entire NeXT community *wishes* all the Apple freaks would realize every now and then.

  2. If someone runs it... by Hal-9001 · · Score: 2, Insightful

    ...it's not dead. Obsolete computer systems don't die--they just get severely marginalized...

    --
    "It take 9 months to bear a child, no matter how many women you assign to the job."
    1. Re:If someone runs it... by Anonymous Coward · · Score: 0

      people fuck corpses, but they're dead as well.

    2. Re:If someone runs it... by Anonymous Coward · · Score: 0

      You fuck your operating systems? That's fucked up... :-p

  3. She was good by Anonymous Coward · · Score: 0

    I messes around with the BeOS on my p120. It was fast as hell but it was near the end so there wasn't much around to actually do!

    1. Re:She was good by Squarewav · · Score: 2

      I messes around with the BeOS on my p120. It was fast as hell but it was near the end so there wasn't much around to actually do!

      I loved beos, it was a great little OS super fast loading with hardware detection each time it loaded, a fast responding GUI, possibly the best File system ever, but one thing it lacked that really killed it was the fact that there was never any good software for it, the included web browser (net+) was the best you could get for the system and it dint support java/java script/flash or anything else. because it lacked hardware OpenGL there was never any games for it. and the apps that were available such as newsreaders and email clients were basic at best and tended to crash. even with all that I would still be
      running it if it wernt for the fact it doesn't support my hardware anymore, but thats what happens when a company goes under

    2. Re:She was good by Anonymous Coward · · Score: 0

      What you describe is called the development process. Since that day, we have ported Mozilla, have a perfectly capable newsreader called PineappleNews, there's a group porting Java 1.4 with help from Sun, we have a Flash plugin that works with Mozilla (though it's incompatible with Flash6, unfortunately). All our email clients are perfectly capable with MDR, Beam and Scooby (all email clients).

      Give Be another go, if not just for the heck of it. There's plenty of software available and still more coming down the line.

    3. Re:She was good by cioxx · · Score: 3, Interesting
      I loved beos, it was a great little OS super fast loading with hardware detection each time it loaded, a fast responding GUI, possibly the best File system ever

      Funny you should mention that. Next release of Windows is trying to do just that. Putting a database at the core of an OS. Just like BeOS.

      Afterall, Microsoft = Innovation.

      BFS is superior to the other file systems due to several factors. One is the ability to represent multiple media devices as a single partition or volume. It has advanced caching methods. It greatly optimizied multimedia applications (well, in theory because there wasn't much to play with on BeOS) and was portable, meaning it could be moved between different hardware platforms easily.

      But I'm sure MS coders will fix that =)
    4. Re:She was good by rusty0101 · · Score: 2

      .. with hardware detection each time it loaded,... and was portable, meaning it could be moved between different hardware platforms easily.

      When a motherboard failed on me, I was able to take the hard drive out, and install it in another box, with all different hardware, and the system booted cleanly (with the exception of the network card which ahd to be re-configured.) to a working desktop.

      I Honestly think that with two workstations that have hardware tha BeOS supports, you could use a removable drive tray system to take your hard disk back and forth with you between work and home. My experience is that the workstation would look the same on each platform.

      I will acknowledge that moving it from a 233mhz K6 to a 1GHZ P3 would have a performance impact, as would moving from a 14" CRT to a 17" LCD impact the user's view. When it comes to a user needing to get work done, those are incidental, unless the change prevents you from getting work done.

      I still do use BeOS on at least two systems. One for my multi-media center to stream my music, the other for my old desktop. My current "primary system" is a laptop usually running Mandrake 9.0. For some reason it ain't playing my MP3 files, even though it is perfectly happy to use the sound system to anounce to me that I have e-mail.

      Why do I still use BeOS there? because it works and I really do not see a good reason to move those systems to any other operating system. Might that change? Possibly. At the same time by the time I need to make that decision, OpenBeOS may be an available binary install that I can use. If so, I would be happy to go with that.

      I have used DOS 3.1, 3,3, 4.01, 5.0, 6.0, 7.0 and a couple of open source varients, most Windows varients, several linux distributions including slackware, debian, redhat, caldera, corel, and Mandrake, OS/2 2.1, 3.0, 4.0 and BeOS 4.5.2, 5.0, 5.1 and 5.2 . I have even gotten Plan 9 (one of the early releases) to boot, though not to a production state by any means, and several Macintosh versions.

      Of all of these, _Only_ BeOS installed without a hitch onto any of my hardware, and made use of almost all of the attached peripherals. The world ain't perfect. The closest OS implementation I have seen to "perfect" would be BeOS.

      Could it have used more hardware support? Sure! The APIs have been out there, I suspect that more than a few people would welcome your efforts to help out with more than a complaint that you don't think it supports your Voodoo 5 card. I think that is true even going forward.

      Later.

      -Rusty

      --
      You never know...
  4. I know it hurts... by thammoud · · Score: 4, Funny

    but please let go!! Don't repeat the same mistake I made with Amiga and OS/2

    1. Re:I know it hurts... by zulux · · Score: 5, Funny

      but please let go!! Don't repeat the same mistake I made with Amiga and OS/2

      With a record like that, can I ask you a favor? ....

      Please start running Windows. Thanks for your consideration.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    2. Re:I know it hurts... by SN74S181 · · Score: 1

      Oh, please.

      Contrarians are never gonna mind your suggestions...

    3. Re:I know it hurts... by Anonymous Coward · · Score: 0

      You know they told me to install Windows95 or better... so I installed linux.

      (bet you heard that b4) :)

    4. Re:I know it hurts... by Anonymous Coward · · Score: 0

      Well, I am still using my Amiga at semi-regular times, and before that I had an MSX2 (know what that is?), and the PC I'm typing this on runs Windows (as one of its OS'es ;-) ).

      I have to say, it seems to be helping. People are telling me the PC gamemarket is collapsing; governments are jumping to Linux; and of course M$ seems determined to run Windows into the ground by way of the Palladium sandbank...

  5. mm by Pros_n_Cons · · Score: 4, Funny

    okay maybe its not dead, but its sure starting to smell funny.

    --

    -- "of course thats just my opinion, I could be wrong." --Dennis Miller
    1. Re:mm by selderrr · · Score: 2

      that's the webserver you're smelling :-)

  6. Comment removed by account_deleted · · Score: 5, Interesting

    Comment removed based on user account deletion

  7. Dead or not... by groman · · Score: 5, Interesting

    Dead or not, BeOS was one of the best operating systems I have ever used. If only it had the software/hardware support. It booted faster than DOS(and I'm not kidding), heck, it booted faster than anything else I've ever seen. It had one of the best browsers I've ever seen(Netpositive) and it was very very slim. What they needed is a linux binary emulator and a well designed wine-like windows binary emulator for the software, and a bunch of HOWTOs on how to port BSD/Linux drivers.

    I stopped using it because it didn't support my NIC, and when i sat down to port the driver from BSD i found myself lost in the lack of debugging documentation and gave up.

    Sad. Just sad.

    1. Re:Dead or not... by Reality+Master+101 · · Score: 2

      very very slim

      Simple question: so what? How does that help me get work done? Usually the opposite is true: slim means missing features, which means more work in other ways. Boot speed is irrelevent, except at the start of the day (I leave my computer on all the time anyway).

      --
      Sometimes it's best to just let stupid people be stupid.
    2. Re:Dead or not... by reallocate · · Score: 3, Insightful

      NetPositive seemed rather lame when I used it.

      BeOS was/is a slick OS that deserves most of the praise it receives, but what it didn't need was a Linux binary compatability layer or a working implementation of Wine. People who want to run Windows or Lnux apps are already running Windows or Linux. What BeOS needed was some BeOS-only applications that gave the platform a competitive advantage.

      BeOS was like a shiny new car, all polished but with nowhere to go.

      --
      -- Slashdot: When Public Access TV Says "No"
    3. Re:Dead or not... by karlm · · Score: 3, Insightful
      BeOS is still sitting on /dev/hda2. I loved that the UI was simple, lightweight, and fast. It made me forget that my machine is only 266 MHz.

      However, it had some pretty bad nasties:

      • Woke up one morning to find my floppy drive spinning. Floppy had a notch in it from rubbing on the read head in the same spot all night. Read head died from overheating, I think.
      • Frequent kernel panics
      • Reliable kernel panic from settinga Semaphore
      • NetPositive bookmarks' data stored in the metadata fork of theFS, so tar, cp, et. al. would save the bookmark file, but it was useless because the URL was left behind (Discovered this after reinstalling the OS just in case my kernel image on disk was corrupted. Nothing like installing your backups to discover that some idiot put essentail data in the metadata fork.
      --
      Copyright Violation:"theft, piracy"::Anti-Trust Violation:"thermonuclear price terrorism"<-Overly dramatic language.
    4. Re:Dead or not... by jonadab · · Score: 4, Insightful

      > Dead or not, BeOS was one of the best operating systems
      > I have ever used.
      I won't go that far, but certainly Be had some innovations that other
      OSes would do well to consider. Even today. No, I'm not talking
      about the filesystem.

      > If only it had the software/hardware support.
      I don't think either was really a problem. It had the stuff that
      actually mattered. (Emacs, Mozilla, what else do you need? ;-)
      It ran fine on my hardware. Now, it has problems with some newer
      hardware (USB, 3D acceleration, ...), but that's because its
      development waned and stopped; it was up to approximately current
      at the time of the release of R5. At the time, it had better
      hardware support in some areas than Linux. (For example, BeOS had
      drivers for some software modems before Linux did.) It has rotted
      since things fell apart, but that's a symptom, not the problem.

      BeOS needed two things. Advertising and OEMs. Oh, and there were
      a handful of important missing features, such as the ability to set
      colour prefs globally, but the Mac is _still_ missing that one, so
      it must not be fatal. Java support was lousy, but there have been
      issues with that on the Mac also, as recently as a year ago, so
      again, it must not be fatal.

      BeOS, like I said, needed two thing: advertising and OEMs. But
      instead of trying to sell the system, Be kept trying to sell the
      technology (to Apple, to Palm, to embedded markets, to game
      developers, and who knows where else that they didn't make public).
      I don't know whether they could have successfully sold the system
      as a desktop system, but I wish they would have tried a little
      harder to do that. AFAIK there was never _one_ TV commercial for
      BeOS systems. I know commercials cost money, but look where not
      advertising ended them. You have to try something, and the things
      they tried didn't work.

      > It booted faster than DOS(and I'm not kidding)
      Maybe not kidding, but you're exaggerating fiercely. The time DOS
      required to boot was dwarfed several orders of magnitude by the
      time the BIOS needed to do the POST; to say the same of BeOS would
      be a significant hyperbole. It did boot much faster than Windows
      or Linux, but as the other poster pointed out, boot time is really
      not a big deal to most users.

      > It had one of the best browsers I've ever seen
      Err, I don't know what you saw in NetPositive. It didn't seem like
      a very good browser to me. This really didn't matter though. First,
      most users don't care beans about the quality of the browser (hence
      the popularity of IE4 in its day, which was nothing to write home
      about either), and second, you could download and install Netscape 4
      (which at the time was not seeming so ancient; today of course you
      can get Mozilla for BeOS).

      > and it was very very slim
      That really only mattered for dual-boot scenarios. I will say, BeOS
      is a multibooter's dream come true. "Plays well with others" could
      just about be its official motto. It also had an excellent driver
      model, which basically didn't require any changes when hardware was
      swapped out -- very user friendly, that. HardDrake is only just now
      beginning to approach this. It also had a couple of nice features,
      such as having a different res and colour depth for each workspace.

      > What they needed is a linux binary emulator

      Way more trouble than it would be worth. An X11/GTK+/Qt library
      done as a wrapper around the native GUI would have been orders of
      magnitude easier to do and gained source compatibility, which would
      be plenty good enough. And yeah, I know FreeBSD does it, but OSS
      does a lot of things in different ways from how companies do them.

      > and a well designed wine-like windows binary emulator
      Even harder to do than the Linux binary emulator, because Windows
      is more poorly documented (in terms of its internals and ABI).
      It would also be more worth doing, but the amount of work involved
      could be prohibitive, and performance would probably not be great.
      Besides, OS/2 went down this path, and the only reason they didn't
      go bankrupt is because IBM has lots of other irons in the fire
      besides the OS.

      > I stopped using it because it didn't support my NIC, and when i
      > sat down to port the driver from BSD i found myself lost in the
      > lack of debugging documentation and gave up.

      I think Be made a mistake getting out of hardware. They got out
      because Apple wasn't cooperating any longer, and they ported to
      x86, and as far as it went that was fine, but while offering up
      a version that will run on various x86 hardware with an HCL is no
      bad thing, I think they still should have sold prebuilt beboxen,
      in an x86 variety. And I think they should have marketed them.

      Now, I think Palm should come to terms with the realisation that
      they aren't going to develop BeOS (unless they _are_ doing so, in
      which case great), and get what PR they can out of the deal by
      open-sourcing whatever parts of the BeOS source code they have the
      rights to. (Obviously there would be some pieces of BeOS that were
      sublicensed and could not be released, like there were some bits
      of Communicator and StarOffice that couldn't be released with the
      rest, but that's a minor complication.)

      --
      Cut that out, or I will ship you to Norilsk in a box.
    5. Re:Dead or not... by Bishop · · Score: 2, Insightful

      What they needed is a...

      What they needed was a market. This seems to be a hard lesson for many technical people to understand.

    6. Re:Dead or not... by snarfer · · Score: 3, Insightful

      If they had run so much as a single advertisment, anywhere, any time, perhaps they might have started finding out if there was a market.

    7. Re:Dead or not... by sql*kitten · · Score: 2

      It booted faster than DOS(and I'm not kidding), heck, it booted faster than anything else I've ever seen. It had one of the best browsers I've ever seen(Netpositive)

      It takes more than fast booting and a pretty web browser to make a viable product. There is only one justification for any product and that is its economic viability. Oracle exists because their software makes their customers more productive. Linux exists because the pleasure of working on it is worth more to its developers than the cost of their time and equipment. BeOS simply didn't offer enough value to enough people to be viable.

      In the final analysis, the company spent too much of its resources doing things that would only appeal to people who didn't have much money.

    8. Re:Dead or not... by Anonymous Coward · · Score: 0
      well designed wine-like windows binary emulator

      ITYM "well designed windows binary emulator"

      HTH.

  8. BeBits by joyoflinux · · Score: 5, Interesting

    I guess BeBits is still there and offering software...

  9. Why Be Failed by scott1853 · · Score: 4, Funny

    noticeable speed when usng the find queries..

    Apparently it's missing a spell checker.

    1. Re:Why Be Failed by Anonymous Coward · · Score: 0

      > > noticeable speed when usng the find queries..

      > Apparently it's missing a spell checker.

      Doesn't seem to have hurt Slashdot...

  10. Which is exactly what Be was doing... by Anonymous Coward · · Score: 1, Insightful

    ...and look how wildly they succeeded there. You can look in a thousand video editing suites now and not find one BeBox. They're all using Mac OS X now. Why? Well, aside from the fact that it works better and has a zillion times more software....

    1. Re:Which is exactly what Be was doing... by Anonymous Coward · · Score: 0

      Depends on how you define "works better". It certainly isn't faster.

    2. Re:Which is exactly what Be was doing... by daviddennis · · Score: 2

      I suppose it depends on your definition of working better. I will admit I never used the video editing software on BeOS, although I've used the operating system itself and liked it. But I really doubt that anything for the BeOS would even come close in quality to Final Cut Pro or After Effects.

      It might well be that a BeOS version of Final Cut Pro could have been better, or at least faster, than the MacOS X version. But MacOS X just has more of a critical mass in terms of applications, and sadly that cannot be ignored.

      If it weren't for that critical mass effect, I daresay we'd have a very different - and higher quality - selection of operating systems today.

      I have to admit that the BeOS aesthetic experience never came even close to MacOS X, and that's something that's hard to let go of once you've experienced - even if it is sluggish, it's so nice to look at that it's easy to forgive.

      Maybe I'm just not the speed addict most of you folks are ...

      D

  11. I miss the BeBox - it was great hardware by hillct · · Score: 3, Interesting

    A buddy of mine from school had a BeBox. They were Dual Motorola 68K class (maybe 68040s) boxes. Not only were they pretty damn fast, but they were cool loooking. I recall much hype about these boxes but as far as I know, only a few hundred were ever built. To this day I'm suprised they abandoned the hardware business so quickly.

    Has anyone got Linux or some other OS going on a BeBox? I would expect most of the stuff ported for YellowDog would run without much work, although you might not get load balancing on 68k processors without a bit of kernel hacking

    --CTH

    --

    --Got Lists? | Top 95 Star Wars Line
    1. Re:I miss the BeBox - it was great hardware by techathead · · Score: 1

      Actually if anything were likely to run on it, it would be Debian 68k. Yellow Dog, while a great distro, is PowerPC only, not 68k. To my knowledge there were some folks working on bebox support, however I am not sure what came from it.
      Tommy

    2. Re:I miss the BeBox - it was great hardware by eXtro · · Score: 3, Interesting
      I don't think Be ever produced 68K based BeBoxes. As far as I know they were all dual processor PowerPC. I think at the low end they used one of the PPC603 variants.


      When I looked at BeOS it was a good start. I'd have stuck with BeOS if it would have been closer to unix. Something seemed terribly broken to me logging into a machine that has a shell prompt and automatically being root.


      I can sort of understand that for their target market they were worried about making it look too unfriendly, but you can always have an option of being wide open, but even then I'd prefer to have two tiers of users: administrator and everybody else. I can imagine the world of hurt when the average video production guy got rid of all those files he never used to make room for more video.

    3. Re:I miss the BeBox - it was great hardware by slithytove · · Score: 3, Informative

      they were powerpcs, 603-66s and 603e-133s.
      I miss my BeBox more than I can convey in words:( I'm going to get all bleary eyed if I continue this post, so...

    4. Re:I miss the BeBox - it was great hardware by Anonymous Coward · · Score: 1, Interesting

      The BeBox was PowerPC. It had dual 603s. Otherwise, NetBSD ported to the wrong system.

    5. Re:I miss the BeBox - it was great hardware by am46n · · Score: 1

      NeXT ran on intel/68k. BeOS ran on intel/PPC. There wasn't a 68k BeBox.

    6. Re:I miss the BeBox - it was great hardware by AgtAlpha · · Score: 2, Informative

      Actually, the BeBox has dual 603e PowerPC processors, running at either 66 or 133 MHz. I have a revision 6 motherboard BeBox set up in my room right now. 3 PCI slots, 6 ISA, 3 MIDI, 2 stereo audio out, 1 stereo in, SCSI, PS/2, and an old-school-style keyboard plug. It has 8 slots for 72 pin 60ns non-parity RAM SIMMs. (It will take parity RAM, but the BIOS doesn't do parity-checking, so it doesn't matter. EDO RAM has been reported to work in some cases, but it won't boot with it in mine. The theoretical max of RAM I've heard is 1GB.)

      The original BeBox ran 8 hobbit processors from AT&T, but when they found out they were EOLing the hobbit, they switched to PPC. It also has processor-load LEDs on the front that show real-time CPU usuage.

      There's a port of Linux/PPC for the BeOS, and I believe they also had mklinux running on it. I don't know, as I personally run BeOS 5.0.3 Professional on it. There's a lack of software and drivers, but it has Mozilla, Gobe Productive (awesome office suite from the guys that originally did Claris Works, and was recently open sourced ... there are Windows and Linux versions, too), and gads of utilities at BeBits, including the best audio player anywhere, SoundPlay; it was the first to play an MP3 backwards in real time without skipping.

      Just some info, and thought I'd clear the air. But BeOS definitely isn't dead as an operating system, only BeOS, Inc. is.

      --

      -- Rob
      Y'a jamais des choses qu'on peut pas se débrouiller ; juste laisse-moi t'aider!
    7. Re:I miss the BeBox - it was great hardware by dozer · · Score: 2, Interesting

      What did you do, throw yours out? I kept mine Blinkenlights, GeekPort and all.

      Funny thing: interprocessor interrupt latencies were so high that usually the two 603s just ended up stomping all over each other. Try this some time: run one of Pierre's pheonomenal threaded 3D demos in dual-processor mode. Then turn one CPU off. Watch frame rates go up. :)

      If Be had stuck to its original vision, it would still be a small but successful company today. Gassee had to ruin everything in the name of ego.

    8. Re:I miss the BeBox - it was great hardware by SN74S181 · · Score: 2


      I'd have stuck with BeOS if it would have been closer to unix. Something seemed terribly broken to me logging into a machine that has a shell prompt and automatically being root.


      Actually, some people thought the single user model was one of the virtues of BeOS. It had a lot of Unix-y goodness, but it didn't drag in a multi-user Time Sharing enviroment. Time Sharing environments are fine for servers and multi-user machines, but they're a real waste on a single user desktop machine.

    9. Re:I miss the BeBox - it was great hardware by SN74S181 · · Score: 1

      There's a port of Linux/PPC for the BeOS

      You can also run NetBSD on the BeBox (and it's not yet-another-fork like most Linux distros,) but *ahem* maybe that was already assumed.

    10. Re:I miss the BeBox - it was great hardware by khuber · · Score: 1
      Time Sharing environments are fine for servers and multi-user machines, but they're a real waste on a single user desktop machine.

      Says you. What about a corporate environment where you don't want to give users full access to mess things up? On NT/Win2k/XP, you don't give them Administrator and on Unix you don't give them root. "Users" allow you to isolate processes, group processes, and give different permissions to those processes. It's a nice system even if there's only one human user on a machine.

      -Kevin

    11. Re:I miss the BeBox - it was great hardware by Maniakes · · Score: 1

      I'd have stuck with BeOS if it would have been closer to unix. Something seemed terribly broken to me logging into a machine that has a shell prompt and automatically being root.

      We'd always planned to do this. Multiuser logins was partially implemented during BeOS 5.0 development, but it was pushed back to 6.0 when we moved half our programmers to internet appliances. And Be ended up going out of buisness before 6.0 was finished.

      --
      A legparnasom tele van angolnaval.
    12. Re:I miss the BeBox - it was great hardware by Anonymous Coward · · Score: 0

      I remember seeing a BeBox in action - a friend had one. He was showing me the multiprocessor core in action and how you could click an icon to turn off one of the CPU, to shift all the load immediately to the other CPU.

      "What happens if you now turn off the second CPU?" I asked.

      We clicked on the second icon. The machine completely froze. Magic :)

  12. Cue obligatory endless Monty Python comments by Anonymous Coward · · Score: 0

    It's not dead, it's resting, gone to join the choir invisible etc.

    Although BeOS is effectively dead, an OS is still alive as long as there are people using it and developing for it. BeOS is a nice OS and should not have died, IMO. I think it died because it had a really sucky name.

    1. Re:Cue obligatory endless Monty Python comments by Anonymous Coward · · Score: 0

      Yeah... just like OGG Vorbis, grep, vi, UNIX, emacs, mutt, etc...

      Oh yeah... did you see that Solaris is coming out this December?

      The movie you idiot... not the OS. Oh... never mind.

  13. I would run it by Apreche · · Score: 4, Insightful

    As far as I'm concerned, from a purely technical standpoint, BeOS is the BEst Operating System ever. It has absolutely everythign I've ever wanted. The only reason I don't use it is the lack of software. Can I get photoshop for it? How about Winamp? Icq? Aim? Eudora? Most importantly Half-Life: Counterstrike? Some yes some no. Despite all of its outstanding technical greatness BeOS doesn't have all of the software I need.
    Windows has absolutely everything, and games.
    Linux has everythign I need, or a good equivalent of what I need, and it has tools for developing software.
    So I run windows and Mandrake. I would LOVE to run BeOS, it's got everything I've ever wanted. But no software. Sorrow!

    --
    The GeekNights podcast is going strong. Listen!
    1. Re:I would run it by Anonymous Coward · · Score: 0

      Fucking moronic little kid. Get some fucking priorities.

      Moronic like insulting strangers on Slashdot? Or did you mean something else?

    2. Re:I would run it by ari_j · · Score: 2

      Wait a second...

      It has absolutely everything I've ever wanted ... [insert list of specific things it does not have] ... doesn't have all the software I need.

      I love BeOS, but man...rephrase your thoughts.

    3. Re:I would run it by LoudMusic · · Score: 2

      I was using CLAamp (and still do when I run BeOS). It's just like Winamp.

      And there are clients for all the major IM protocals.

      BeBits

      The mail client was pretty awesome, but I'm sure you can get more at BeBits as well. And I have to agree with someone eles post - if gaming is a priority for you, you're not allowed to be picky about your OS. Get a console system.

      Oh, and there is a Photoshop for Solaris. I'm sure with a little work someone could get it to run in BeOS. But there are plenty of other editors our there. You could run GiMP for BeOS.

      Once again, the OS never really reached maturity. If it had, more people would have been writing software for it. When they chose not to work on a G3/G4 version, they lost the Mac crowd, and that was their biggest market. Adobe would surely not pick them up after that.

      ~LoudMusic

      --
      No sig for you. YOU GET NO SIG!
    4. Re:I would run it by Anonymous Coward · · Score: 0

      Someone sounds bitter!

      Go back to playing Jezzball, Mame (with no hardware acceleration of course), and Tuxracer (if you can get any of them to run).

    5. Re:I would run it by Anonymous Coward · · Score: 0
      When they chose not to work on a G3/G4 version, they lost the Mac crowd, and that was their biggest market. Adobe would surely not pick them up after that.


      A lie occured in the first sentence above. The largest market of BeOS was and is on Intel hardware. G3/G4? Well Be never survived long enough for to support G4 and Apple didn't want them on G3. Intel wanted Be on the x86 line once they saw it running. Intel threw millions of dollars at Be after that.

    6. Re:I would run it by sql*kitten · · Score: 2

      As far as I'm concerned, from a purely technical standpoint, BeOS is the BEst Operating System ever. It has absolutely everythign I've ever wanted. The only reason I don't use it is the lack of software. Can I get photoshop for it? How about Winamp? Icq? Aim? Eudora? Most importantly Half-Life: Counterstrike? Some yes some no. Despite all of its outstanding technical greatness BeOS doesn't have all of the software I need.

      So what you're saying is it had absolutely everything you've ever ever wanted... apart from absolutely everything you've ever wanted?

  14. Obligitory link by Anonymous Coward · · Score: 2, Informative

    http://syllable.sourceforge.net The Syllable operating system isn't meant to be a BeOS clone, but it's fairly mature and it is targetted to turn out much like it. BeOS fans and people with technical skills may like to take a look.

  15. I think BeOS is dead, usefulness-wise by Knife_Edge · · Score: 4, Insightful

    My major clue is that the install process seems to still require the making of a 1.44" boot floppy. That is, if you want to run it by itself, outside of another OS.

    To me this speaks volumes about just how old it really is, and probably indicates it is never going to be updated to modern hardware. Also, what makes it relevant in this day and age? Can it do anything another system cannot do better? If the answer is no, or even an extravagantly technical yes (which would never matter to most users), then the world has passed it by.

    The impact of BeOS was probably like Ross Perot in the 1992 presidential election. He lost, but got a large enough percentage of the vote to scare the mainstream politicians into sharpening up their act. I think this is arguably one of the factors for the prosperity of the 1990s. If I am correct, we can thank BeOS for encouraging other software makers to improve their quality/performance. Therefore BeOS benefits us even now, but we do not get the benefit from actually using it.

    1. Re:I think BeOS is dead, usefulness-wise by AvitarX · · Score: 4, Interesting

      The most interesting thing I ever did on BeOS was open the same mp3 about 30 times (at least) and had them all playing at once. Eventually the mp3 player crashed so that any new instances didn't work, but the playing ones did still work and finished up. I was really impressed. Also even under all that load the desktop was as responsive as kde 2. This was a 450 Mhz PIII. I was absolutly amazed.

      As an aside, does anybody know what happened to Corum III (It was a secret of manaish game that was going to be released). I loved the demo, but was not going to pay for it on many month preorder, the company claimed to go gold, and yet never released their product. I could not find any references to the series on the net, and the only references to the 3rd one were for BeOS. Was this not really a port? I really wanted to play this game.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    2. Re:I think BeOS is dead, usefulness-wise by be-fan · · Score: 2

      I've got a copy of the game right now. It's pretty good, but no Secret of Mana :) Methinks you're looking in the wrong places. Gobe was offering a bundle of BeOS 5 Pro and Corum III awhile back.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:I think BeOS is dead, usefulness-wise by Anonymous Coward · · Score: 1, Informative

      Information on Corum III for BeOS
      http://www.gobe.com/storecorum3.html

      Place where you can buy Corum III for BeOS
      http://www.gobe.com/order.html

    4. Re:I think BeOS is dead, usefulness-wise by AgtAlpha · · Score: 2, Informative

      BeOS never required a boot disk. The installation CD boots, and lets you manage your paritions from there before installation. You can also do a fully-booting installation from an BeOS partition to another (well, a booting one at least). As for the remark regarding BELO (what's that), BeOS's boot loader was called bootman, and was usually installed in the MBR. Far easier than LILO to set up. Run bootman, select the partitions to want to show up in the boot menu, give them labels, choose a defualt, and click OK. Couldn't be easier. I use it for Win2K, Win98, BeOS, and Linux.

      --

      -- Rob
      Y'a jamais des choses qu'on peut pas se débrouiller ; juste laisse-moi t'aider!
    5. Re:I think BeOS is dead, usefulness-wise by Anonymous Coward · · Score: 0

      i think the word *never* doesnt mean what you think it means

    6. Re:I think BeOS is dead, usefulness-wise by Hal-9001 · · Score: 1

      I liked the demo where you could render movies onto different geometric objects by dragging and dropping them. I'd have 6 movies playing simultaneously on a spinning cube, with another couple MP3's playing, some forwards, some backwards... ;-)

      --
      "It take 9 months to bear a child, no matter how many women you assign to the job."
    7. Re:I think BeOS is dead, usefulness-wise by Anonymous Coward · · Score: 0

      To me this speaks volumes about just how old it really is, and probably indicates it is never going to be updated to modern hardware. Also, what makes it relevant in this day and age? Can it do anything another system cannot do better? If the answer is no, or even an extravagantly technical yes (which would never matter to most users), then the world has passed it by.



      It is easy to use! Linux and Windows are not. End of discussion.

    8. Re:I think BeOS is dead, usefulness-wise by Fjord · · Score: 2

      Windows XP Pro and Windows 2000 requires you to make boot disks if you don't have some version Windows already installed. It's a pretty big pain in the ass.

      --
      -no broken link
    9. Re:I think BeOS is dead, usefulness-wise by lucifuge31337 · · Score: 2, Informative

      Huh? They are both distributed on bootable CD's.
      Sounds like your dated hardware requires you to make boot disks.

      --
      Do not fold, spindle or mutilate.
    10. Re:I think BeOS is dead, usefulness-wise by Tofuhead · · Score: 2

      As an on & off user of BeOS when it was still being actively developed, I'd never really kept up with the BeOS news outside of whatever was presented in general tech news (like /.). So, although I'd never heard of this game before, I'm glad that you brought it up. I'm downloading the demo as I type this.

      To respond to your question of whether this game is really a port from Windows: On the developer's website (link obtained from page at another poster's gobe.com link), I noticed that the "Corum III" logo had a Korean subtitle. So, I'm guessing that the reason you can't find info on the Windows port is that it was likely developed in Korea, and the websites with relevant info would have been in Korean.

      HTH.

      < tofuhead >

      --
      It is still the dark of night.
    11. Re:I think BeOS is dead, usefulness-wise by Suppafly · · Score: 2

      My major clue is that the install process seems to still require the making of a 1.44" boot floppy. That is, if you want to run it by itself, outside of another OS.


      Nice troll, but if thats they only clue you have, you better keep looking as its extremely easy to make a bootable cd from the free version assuming you know how to use cd burning software, and the pay version comes on bootable cds and has boot floppys for the small minority that don't have bootable cdrom drives.

    12. Re:I think BeOS is dead, usefulness-wise by Suppafly · · Score: 2

      BeOS's boot loader was called bootman, and was usually installed in the MBR. Far easier than LILO to set up. Run bootman, select the partitions to want to show up in the boot menu, give them labels, choose a defualt, and click OK. Couldn't be easier.

      I agree, bootman is the easiest bootloader I've ever seen although I have heard that underneath its just lilo, the gui makes it simple to use. I even use it on systems that don't have beos installed.. Just boot up a cd which has a working beos image on it instead of a installer and you can run bootman and have your booting preferences setup with no problems.

    13. Re:I think BeOS is dead, usefulness-wise by dr.badass · · Score: 1

      Many *pirated* copies of Win2k/WinXP won't
      boot from the CD, because the original pirate-er
      just copied all the files, and didn't do a bit-for-bit clone.

      How do I know this? Um...a friend told me.

      -DoctorB

      --
      Don't become a regular here -- you will become retarded.
    14. Re:I think BeOS is dead, usefulness-wise by lucifuge31337 · · Score: 1
      --
      Do not fold, spindle or mutilate.
    15. Re:I think BeOS is dead, usefulness-wise by Watts+Martin · · Score: 2

      None of the Intel releases of BeOS required the install floppy. I can say this pretty conclusively, since I was in the developer program and installed all of them from CD.

      At risk of being a little curt, when you start off by announcing to the world Hi! I've never used this product!, there are volumes being spoken, all right--none of them are about BeOS, though.

      As for what Be can do that other systems aren't doing better, I still miss the "live query" aspect of the system that let you make virtual folders. You could have a folder on your desktop that contained all C source code files you'd modified in the last 24 hours, or all unread email messages from your boss, and they'd always be current (leave the folder open and its contents would change as appropriate). That's a small thing, but most of what I miss about BeOS, ultimately, are small things that few other people seem to have picked up on. OS X is inching there, with things like the systemwide address book and the new search functionality, but it has a ways to go.

    16. Re:I think BeOS is dead, usefulness-wise by AgtAlpha · · Score: 1

      Well, as far as I can recall (going back before R3), BeOS never *required* a boot disk. The instance in which a boot disk was being mentioned was to access the VFS installation on a FAT32 parition for BeOS Personal Edition on Intel/x86.

      All PPC versions, IIRC, installed a boot-loader in the MBR.

      --

      -- Rob
      Y'a jamais des choses qu'on peut pas se débrouiller ; juste laisse-moi t'aider!
    17. Re:I think BeOS is dead, usefulness-wise by Fjord · · Score: 2

      The PCs I have here boot the debian install discs fine, but don't boot the Windows XP or 2000 discs. The 2000 wasn't a pirated discs, as another person in this thread suggested. It had the whole funky hologram on the label side etc etc. The XP one was a backup but I don't know how it was done (incidentally, the installs I've done are for work so they aren't "warez").

      The knowledgebase article for creating the floopies are here for 2000 and here for XP.

      --
      -no broken link
  16. BeOS for the Mac by Asterax · · Score: 0

    Can't certain versions of BeOS run on a Macintosh?

    1. Re:BeOS for the Mac by Squarewav · · Score: 2

      All versions of BeOS(with the exception of the download version) can run on Pre G3 PCI macs (Be claims apple changed how to interact with the hardware making it impossible for beos to load) but if you bought it the cdrom was a hybrid
      that would boot on them.

      the PPC version was getting less and less suport once the G3's came out

    2. Re:BeOS for the Mac by PythonOrRuby · · Score: 2

      I believe BeOS 5 Persona Edition would run on pre-G3 PowerMacs, but after that it went x86-exclusive. Might be a good way to revive an old Mac, though. I'm sure someone else here will or has posted the link to the free download.

  17. A better perspective is... by rampant+mac · · Score: 3, Informative
    an article from Low End Mac, titled: Why BeOS Lost by Chris Lozaga.

    Example?

    Not-quite-Unix

    BeOS had a powerful command line and Unix-like underpinnings that could compile and run POSIX compliant software. Every Unix-like operating system has failed in the marketplace except Linux (which is free, and for all intents and purposes it is Unix). The Amiga Operating System was developed with similar goals in mind, and that particular operating system withered and died as well. Being able to compile POSIX compliant software is not a marketable advantage (even Windows NT can do it).

    It's an interesting article, and I think it sums up why BeOS really failed. I truely liked BeOS, but not for my main desktop.

    --
    I like big butts and I cannot lie.
    1. Re:A better perspective is... by mmu_man · · Score: 2, Interesting

      The difference with NT being integration.
      BeOS uses bash as its shell, NT uses the ugly CMD.EXE...

      As for desktop use, well I've been using BeOS as my primary OS for a year now, and I'm very happy with it.
      It does what I need, I play DivX on my K6-2 350, listen to mp3/ogg files and streams, burn CDs, devel, surf, ...

    2. Re:A better perspective is... by Anonymous Coward · · Score: 2, Insightful
      BeOS had a powerful command line and Unix-like underpinnings that could compile and run POSIX compliant software.
      Um, good try for a Mac user, but no. It can compile and run some POSIX software, so long as that software doesn't happen to use features BeOS doesn't implement... But BeOS is by no means POSIX compliant. It lacks a lot. Off of the top of my head, I can tell you that it lacks mmap() for example.
      Every Unix-like operating system has failed in the marketplace except Linux
      So you're saying that Solaris has failed?

      If you want to take it a step further, you can say that most, if not all modern operating systems are somewhat "Unix-like" in that they all implement features from Unix libc.
    3. Re:A better perspective is... by Anonymous Coward · · Score: 0

      AmigaOS is almost the total opposite to UNIX.

      AmigaOS: realtime, microkernel, loadable drivers, single user, one-level file systems, no memory protection or virtual memory (ie. no fork), excellent multimedia support, friendly commandline, ...

      UNIX: time-sharing, monolithic kernel, only delayed loading for drivers, multi-user, two-level file systems, memory protection and virtual memory, laughable multimedia support, arcane commandline, ...

    4. Re:A better perspective is... by sql*kitten · · Score: 2

      Being able to compile POSIX compliant software is not a marketable advantage (even Windows NT can do it).

      Oh yes it is. If you can't compile POSIX apps then you aren't FIPS compliant and it's extremely unlikely that the government will ever buy or use your OS. That's the one and only reason NT has it.

  18. mmm... troll food by Theodore+Logan · · Score: 2, Funny

    with the amusing conclusion that BeOS isn't dead after all!

    Not dead, but probably dying. And a couple of hundred trolls are willing to prove it to you. In related news, Natalie Portman was recently found to naked and petrified pour hot grits down the pants of a beowolf cluster.

    This is probably a good time to check the "No Score +1 Bonus" button.

    --

    "If you think education is expensive, try ignorance" - Derek Bok

    1. Re:mmm... troll food by Anonymous Coward · · Score: 0

      Slashdot needs a -1, What the Fuck moderation.

  19. My Experience with BeOS... by ElGuapoGolf · · Score: 2, Interesting

    I tried the BeOS a few years back, when the company was around, and they had released some sort of "Preview Edition" which installed itself as one large file on your FAT partition, and you booted into that. The same as some Linuxes do..

    Anyhow, I played around with it for a day or two, then nuked it. Why? Two simple reasons.

    It did not detect or configure my network card. And it wasn't really clear how to do that. Linux installers do that, and have done it for years.

    It didn't detect or configure my video card. And when I followed the instructions on doing so, the BeOS wouldn't boot.

    So that was it for the BeOS. Maybe the full version would configure everything during it's installation; but why would I pay to find out?

    So yeah, I do feel sad when people go on about the death of the BeOS. But I have much more compassion for the OS/2 users. That installed right (mostly), and I lived with that for 4 years.

    1. Re:My Experience with BeOS... by dinivin · · Score: 2

      It did not detect or configure my network card. And it wasn't really clear how to do that. Linux installers do that, and have done it for years.

      It wasn't really clear? Going to preferences from the Deskbar and selecting "Network" wasn't clear? Wow...

      Dinivin

    2. Re:My Experience with BeOS... by sk8king · · Score: 1

      Did the same thing with BeOS....downloaded the personal edition and within five minutes of booting up for the first time, I was connected to a dial-up Internet connection and could contact the other computer on my home network [the linksys card I had was immediately recognized].

      I was mostly impressed by program sizes compared to Windows versions....~50K for an image viewer [maybe, can't remember the exact type of program or size] compared to >~1MB for a Windows program for the same purpose...and it wasn't just a single program, every program was like that.

    3. Re:My Experience with BeOS... by bedouin · · Score: 1

      Maybe it just wasn't clear to him because he thought a menu showing choices for only two different kinds of network cards /had/ to be a mistake, and fixable in some way.

    4. Re:My Experience with BeOS... by ElGuapoGolf · · Score: 1
      Maybe it just wasn't clear to him because he thought a menu showing choices for only two different kinds of network cards /had/ to be a mistake, and fixable in some way.

      Yeah, pretty much that. It's not like I had exotic hardware; in fact it was fairly common (Realtek card of some sort). I tried everything I could find on the web to get it working, and nothing did.

      The system did *look* impressive; at least until I tried a better video driver. Then it wouldn't boot.

      And people say Linux is hard to use?
    5. Re:My Experience with BeOS... by snarfer · · Score: 2

      It did not detect or configure my network card.

      The criticism of BeOS not supporting enough hardware is actually a good way to point out the effect of the Microsoft monopoly on competitors like Be. By preventing OEMs from putting BeOS on their machines, Microsoft killed off the possibility of BeOS getting enough traction to get started.

      Companies write drivers for Windows because of its market share. If OEMs had started including BeOS there would be more developers writing software, which would mean there were more people ready to buy BeOS, which would mean companies writing drivers for their hardware.

    6. Re:My Experience with BeOS... by ElGuapoGolf · · Score: 1
      The criticism of BeOS not supporting enough hardware is actually a good way to point out the effect of the Microsoft monopoly on competitors like Be. By preventing OEMs from putting BeOS on their machines, Microsoft killed off the possibility of BeOS getting enough traction to get started.

      This may indeed be true. But OS/2 and Linux had no trouble supporting them. And OS/2 was long since "dead" by this time, and the BeOS was still being actively developed.
    7. Re:My Experience with BeOS... by Kreeblah · · Score: 1

      Actually, the BeOS does a very good job of dealing with hardware configuration, provided there are drivers for the hardware available. If there is, it's configured automatically. It just works (except for network cards, where the extent of the configuration is choosing among DHCP, manual IP config, or disabled). If there isn't a driver for the device, it doesn't work (or goes grayscale, in the case of the display).

      This can really be seen if you have two different BeOS-supported video cards. Swap them out and the box will boot as though nothing happened. Now if only other operating systems could do that . . .

    8. Re:My Experience with BeOS... by margaret · · Score: 1

      I tried BeOS around this time too - release 5 I think. I really liked it, and I even bought GoBe Productive to replace Office. Unfortunately, I could never get the damn sound card to work. It wasn't entirely Be's fault though - my crappy Gateway motherboard didn't have an option to disable plug-and-play, and that was apparently screwing things up. (One thing I did find out - Be users are extremely nice to newbies) I bought a second sound card, but that didn't work either, so I evfentually gave up. My experience with Be did open my eyes to what a terrible operating system Windows is though. Seeing the same computer run twice as fast in Be was pretty dramatic. It's probably part of the reason I have a mac now. I love my ibook and OS X is way better than windows, but sometimes when the aqua interface is a little sluggish, I wonder what things would be like if apple had bought Be...

      Oh yeah, and I miss the haiku error messages :-)

  20. Not dead? by pla · · Score: 1, Troll

    Yeah... Suuuuuuuure. Next you'll tell us that legendary beast called the "Mac" still lives. ;-)

    And, of course, we can't ignore that ultra hard core group of Amiga users. Any day now, one of the many compnies that have shuffled *that* hot potato around will release the new-and-improved Amiga, with something better than the 68060. Uh-huh. Sure. And my Atari 800 runs Windows XP.

    I love articles like this one. No one actually used BeOS when it *did* really exist, thus its demise. Why should it matter that some poor deluded bastards still have a dusty, unused partition running it? I still have a DEC Rainbow in my basement, that I occasionally turn on and run NetHack with. That doesn't somehow make Digital any more "real".

    1. Re:Not dead? by Anonymous Coward · · Score: 1, Interesting
      Yes, but it still makes Digital "alive" if someone's using it and developing software for it. The Be community, though somewhat diminished, is still alive and kicking:
      • New software is released to BeBits daily
      • There's around 100 users currently on BeShare (our BeOS-only filesharing client)
      • OpenBeOS has made incredible progress. Our kernel is coming together, a few components have reached beta stage (and more are approaching it)

      So knowing these three things, can you still explain to me why you think the operating system is "dead"? We're far more active and organized than the Amiga or OS/2 communities. Heck, we even benefit from many open-source projects like VideoLAN, OpenOffice, etc .. projects that have BeOS ports and are in heavy development.

      We're not dead by any means and we really don't care what anyone thinks about us still using it. We're not the type of people who need to know that our operating system is going to survive. Certainly we are going to try and save it (and I believe we will), but we're mainly still using BeOS because BeOS still offers quite a bit that other operating systems don't and never will offer. If you don't know those things it might be a good idea to give Be a second chance.
    2. Re:Not dead? by pla · · Score: 2

      Wow, apparently I pissed off some overly touchy people with my post... Two "troll" votes? Humor, people, learn to recognize it.

      That said...

      I call such systems "dead" because, at their most basic level (OS support), they have ceased to exist. It doesn't matter *how* many 3rd party developers support it if, in five years, it doesn't have any support for the latest and greatest hardware.

      Take my specific mention of the Amiga - Yeah, I would agree 100% that, even compared to "modern" GUI-based OSs (Except possibly Darwin), it rocked. Good luck finding replacement parts if the break, though, and don't even *think* about using the latest-and-greatest parts. And hey, it can play Quake - at 10fps.

  21. It's Too Bad, Really by IronTek · · Score: 3, Insightful

    While I do have an affection for obscure operating systems (and the BeOS is certainly now that), the fact that BeOS is obscure is not what makes me admire the damn thing so much.

    As the article says, it was well designed from the beginning, and well thought out through the end. The same can not be said for any other recently modern OS, really, save for maybe OSX (and this requires one to look at OSX as a "new" OS).

    Windows certainly doesn't qualify, and even Linux (which I use and love a great deal) was never initially designed or thought out to be the OS it is today. It's been hacked together over the years to add features like the ones that were in the BeOS from the start (not that the hacks haven't been good...they have...but they're still hacks)...In a way, I'm quite disappointed that Be lost out. There's still always the hope that Palm might do something fun with them, but they'll probably just screw it up... ...now if only I could find a BeBox on the cheap!

    1. Re:It's Too Bad, Really by Linux+Ate+My+Dog! · · Score: 1

      Well, there is the fact that they didn't actually have time to cruft up their design. It was written for a multi-processor abstraction layer, and the team added the latest ideas availabkle in the marketplace. However, they esseintially stayed during their lifetime in the same class of boxes and applications. They didn't get a decade of use in various settings to have to adapt to.

  22. /.'d by Gyorg_Lavode · · Score: 1

    Sites slashdotted, can someone post the text or a mirror?

    --
    I do security
    1. Re:/.'d by Anonymous Coward · · Score: 0

      Mmmmmmmm, no.

    2. Re:/.'d by subuni · · Score: 1
  23. Pot, its the Kettle. Says you're black. by banzai51 · · Score: 0, Flamebait

    Ah Zealots. Aren't we fun? That's rich comming from the (loud) mouth of linux, Slashdot. What's the matter guys, don't like the image you see in the mirror?

    1. Re:Pot, its the Kettle. Says you're black. by Anonymous Coward · · Score: 0

      Duh, he already acknowleged that. He said "we", not "they".

  24. I dunno about BeOS by IIRCAFAIKIANAL · · Score: 2

    but that server is as dead as Disco

    --
    Robots are everywhere, and they eat old people's medicine for fuel.
    1. Re:I dunno about BeOS by Anonymous Coward · · Score: 0

      Disco is not dead!
      Disco is life!

    2. Re:I dunno about BeOS by Anonymous Coward · · Score: 0

      Disco is dead?!?!?!?!

  25. Revisionist BeOS History? by allenw · · Score: 1
    I think it is interesting that he skipped over the pain and suffering the PowerPC developers had due to the horrible build tools. CodeWarrior (unless you did some MAJOR hacking on gcc) was the only compiler you were able to use, as BeOS/ppc used PEF instead of something sane. No decent build tools=no decent apps, which in turn lowered the amount of early adopters you potentially had.

    How about the gloss over of single-user? With the general introduction of networking to the masses, never mind the security implications, why would anyone want to use a single-user OS anymore?

    Did they ever fix the printing subsystem to be useful? For a 'media OS' (good to see JLG still has his marketing skills), the printing support wasn't that great...

    It is also well known that BeOS took the best features from a lot of different OSes... to say "with features built years ago that only today are companies putting into their future OS releases" is a bit much. Most of the features in BeOS were available on most major Unix platforms, even then. In comparison, it is perhaps better to say that BeOS had a 'clean slate' implementation of those features.

    BeFS, however, was really the crown jewel... and probably the only thing really worth saving.

    1. Re:Revisionist BeOS History? by roybentley · · Score: 1

      people still use windows 95 and 98 today. it's a multiuser as beos, except beos doesn't pretend to be multiuser.

    2. Re:Revisionist BeOS History? by jonadab · · Score: 1

      > why would anyone want to use a single-user OS anymore?
      Most people who use a multi-user OS treat it as if it were
      a single-user OS. Actually, most people treat it (it being,
      if we're talking about most people, Windows) as if it were
      a single-tasking OS. I don't think the single-user issue
      was significant to the demise of Be.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    3. Re:Revisionist BeOS History? by Anonymous Coward · · Score: 0

      Your information is a little out of date. The earliest versions of BeOS did indeed use PEF and Codewarrior, but by version 4 (I believe) it was using GCC and ELF binaries.

  26. The latest vers don't require a floppy by slithytove · · Score: 4, Informative

    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.

  27. Lots of innovation by scott1853 · · Score: 4, Troll
    For those that don't want to read the article, I don't blame you because it's poorly written. But here's the summary of it.

    Be's most exciting innovations that other systems are just starting to add support for (according to the article):

    Multi-threading

    Stability

    MIME Types

    Being able to open JPEG files

    Biggest downside:

    Doesn't support USB.

    I don't know what he was using for a comparison but I would assume something console based from MS, circa 1988.

    1. Re:Lots of innovation by Anonymous Coward · · Score: 0
      Gee, what innovation is that? UNIX came up with threaded multitasking with SVR4 (correct me if I'm wrong). Stability, sure, but lotsa other platforms are stable, like BSD or even XP for that matter. Okay, but what platform dosen't have support for MIME type? And Windowz had support for JPEG ever since it's conception. Where you getting your facts from? They are obviously from several decades ago if other platforms are only 'beginning to support JPEG, multi-threading, etc.'

      Well, actually, I wasn't targeting whomever I posted this in response to, but more targeting the article. It's filled with misinformation if that's what it said.

    2. Re:Lots of innovation by be-fan · · Score: 2

      The whole JPEG thing was stupid (I think he might have been referring to something about videos), but the MIME and multithreading is dead on. Sure UNIX and Windows have had multithreading for awhile, but they still don't do it as well as BeOS. BeOS had threads everywhere. That meant that even if the system was nearly brought to its knees with load, it still felt responsive. My 2 GHz P4 running KDE 3.x (Gentoo, uber-tricked out) still doesn't match the responsiveness of my 300 MHz PII running BeOS (dead stock, no tweeking), though its getting close thanks to 6x the processor and 10x the RAM. People complained it was harder to program because of the insistence on threads, but I personally think it was just different, and hard to get used to unless you learned it that way from the beginning. As for the MIME support, sure every OS supports it, but which ones use it as the standard file typing mechanism? BeOS stored the MIME type of a file in an attribute, and had a registrar that automatically detected the type of new files as they were added to the system. This, combined with an utterly flexible mechanism of defining type handlers resulted in the ultimate file typing solution.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:Lots of innovation by Anonymous Coward · · Score: 0

      You know that threads can be double-edged sword , right ?
      With every thread you create you pay a fixed price ( context switch) , the price you would not have to pay without that thread.

    4. Re:Lots of innovation by khuber · · Score: 1
      Does Gentoo have the preemptive kernel patch? If not, you may want to try it.

      -Kevin

    5. Re:Lots of innovation by Anonymous Coward · · Score: 0

      Sure UNIX and Windows have had multithreading for awhile, but they still don't do it as well as BeOS.

      What, you managed to completly miss the announcment concerning the new threads implementation for Linux 2.5? Sorry to tell you this, but Linux now does thread creation, deletion and switching way faster than BeOS could ever hope. The low latency and pre-empt patches, also in 2.5, means that Linux can out perform BeOS on the same hardware.

      which ones use it as the standard file typing mechanism?

      KDE and Gnome on any Operating System, and this one.

      Seriously. BeOS was good in its day, but just because someone wrote an ill informed article that declares BeOS great because it has protected memory (Seriously. Go read the article) doesn't make it so. Give it up, and stop poking it with that stick of yours.

    6. Re:Lots of innovation by khuber · · Score: 1
      Gentoo sounded interesting so I went and read up a little.

      Here's the answer to my question:
      "Our new kernel is based upon 2.4.19 and includes Robert Love's preemptive kernel and scheduler-hints patches, Ingo Molnar's O(1) scheduler and smptimers patches, and Rik van Riel's reverse mapping patches, for enhanced responsiveness and scalability under high loads and in high-end multiprocessor systems."

      O'Reilly Gentoo article

      I may give Gentoo a whirl. Mandrake is getting stale.

      -Kevin

    7. Re:Lots of innovation by Anonymous Coward · · Score: 0

      What, you managed to completly miss the announcment concerning the new threads implementation for Linux 2.5? Sorry to tell you this, but Linux now does thread creation, deletion and switching way faster than BeOS could ever hope. The low latency and pre-empt patches, also in 2.5, means that Linux can out perform BeOS on the same hardware.


      Please link to the speed results of Linux 2.5. Because everyone here knows that this is could never be hype.


      Also do you know how BeOS accomplished thread handling? If you do please explain; otherwise go back to trolling.

    8. Re:Lots of innovation by be-fan · · Score: 2

      Actually, a thread switch is significantly faster than a context switch. x86 machines don't have a lot of state. EROS can do a thread save and restore in about 20 clock cycles, and Linux is known for very fast thread switching, so I doubt it's much slower. It's not like a full context switch where the TLB gets flushed and the cache gets blown. Besides, modern processors can handle thousands for process (not thread) switches per second without any noticible performance impact. That said, threads, even with a speed hit, are worth it. BeOS wasn't a blazingly fast OS in many cases. tar/gzip would run about 10-15% slower under BeOS than under Linux. But users don't really care about a few seconds difference in tarring a file, but care a lot about even 1/3 a second difference in UI response time.

      --
      A deep unwavering belief is a sure sign you're missing something...
    9. Re:Lots of innovation by be-fan · · Score: 2

      Actually, I've been using hacked up preempt/XFS kernels for awhile. But I'm lazy, the default xfs-sources doesn't include preempt (with good reason, they conflict with XFS), and my P4 is fast enough that I don't notice :)

      --
      A deep unwavering belief is a sure sign you're missing something...
    10. Re:Lots of innovation by Suppafly · · Score: 3, Informative

      Biggest downside:

      Doesn't support USB.


      Thats not quite correct considering that my usb input devices work fine under beos without any added configuration. It might not have supported every usb device, but basic ones were supported.

    11. Re:Lots of innovation by Ninja+Programmer · · Score: 1
      • Multi-threading
      This has been in every RTOS since forever, and was first introduced to the mainstream on the Amiga.

      • Stability
      The BSD folks are rolling their eyes.

      • MIME Types
      Wasn't this added to the Emacs OS?

      • Being able to open JPEG files
      I have never run across an OS where this has been a problem.
    12. Re:Lots of innovation by Anonymous Coward · · Score: 0

      Please link to the speed results of Linux 2.5. Because everyone here knows that this is could never be hype.

      Ahhh, and I'm sure your figures are completly unbiased, arn't they?

    13. Re:Lots of innovation by Anonymous Coward · · Score: 0

      do you know how BeOS accomplished thread handling?

      Do you know, I tried to find out. Nothing. Not even the BeBook mentions threads. So, I'm guessing, but lets see....lightweight kernel threads? So? Is there something special and magical about how BeOS handled threads? I don't get it. Seriously. There must be some serious reality distortion fields surrounding BeOS; you only have to look at the wildly optimistic rantings of any OBOS developer to see that.

    14. Re:Lots of innovation by Anonymous Coward · · Score: 0

      That's probably because most PC BIOSes have emulation code that makes a USB HID Keyboard and mouse appear as a PS/2 keyboard and mouse. This is often called something extremely uninformative like "USB Support" in the BIOS options menu - the option means BIOS support for USB.

  28. hey now, Taco's an OSX man... by mtec · · Score: 1

    ...so he can be haughty.

    --
    Cake or Death? Cake Please!
    1. Re:hey now, Taco's an OSX man... by FatRatBastard · · Score: 1

      Cake or Death? Death.... no no no Cake.

  29. BeOS might not be dying by kbroom · · Score: 1

    But that webserver is about to die with the frantic slashdotting is taking.

  30. I'm suprised that it lasted even this long by gotr00t · · Score: 1
    I just honestly can't find out what is so great about BeOS(besides the speed, but what good is speed when there is nothing to do WITH that speed?). Linux and BSD are all based on the time proven UNIX system foundation, but BeOS totally came out of left field, as it isn't open source, nor is it compatible, nor is it good for server platform (we all know that M$ dominated the desktop platform) moreover, it has terriable hardware support and software support, even worse than BSD or Linux. BeOS, with the presence of Microsoft, was never going to succeed, for it was aiming for the desktop platform using a commercial approach, exactly what Microsoft was doing. What chance did they have? None.

    Of course I can agree that BeOS isn't dead, as there is a still an avid userbase. But besides that, the development on that is slowing down to a crawl. I just hope that OpenBeOS will have much success, as it would restore the OS as an open source project, giving it a chance to actually see daylight, and possibly taking a chunk out of the large M$ market share.

    1. Re:I'm suprised that it lasted even this long by strat · · Score: 1

      The pervasive multithreading was a great thing. Rather than hanging bags on the side of legacy systems, they designed a system from the ground up with goals like minimal latency through the kernel, logical API's, pervasive multithreading, and super-easy-to-use IPCS.

      All in all, not surprising.

  31. Are you on crack? by Inoshiro · · Score: 1, Troll

    Net+ was the worst browser! It was like Opera v2, or the brower from IBM that came with OS/2. The entire point of it was to go get a better browser. The only problem was that there never was a good browser, since there was no might like IBM's to get Netscape to port over to the OS (back before Mozilla had enough strength to stand on its own).

    No CSS, HTML 3.2 barely, no JS.. While I don't like JS (I leave most of it off it Mozilla), a lot of sites (ab)use it to perform basic things that should be done at a lower layer, like browser redirects and URL construction. Net+ was impossible to use on anything other that Be's HTML documentation.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Are you on crack? by Xcott+Craver · · Score: 1

      I certainly wouldn't call NetPositive the "best" browser (or even the "best" bare bones browser I've seen,) but I think you're going a bit overboard. It renders most web sites I frequent (including Slashdot,) and I use it over Mozilla whenever I can.

      NetPositive's big problem is that it lacks support for, well, damn near everything. Its advantage is that it launches and renders speedily and gracefully, while Mozilla lurches and grunts. RRRAAAR, MOZILLA SMASH!!!

    2. Re:Are you on crack? by Suppafly · · Score: 2

      The only problem was that there never was a good browser, since there was no might like IBM's to get Netscape to port over to the OS

      When you don't know what you are talking about, its generally better to just not say anything at all.. but oh well.. I see someone has already modded you as the troll you are so no harm done.

  32. My msitake it was PPC by hillct · · Score: 2

    Yah, after a few replies correcting me, I guess it was a PowerPC box. I only ever saw the thing once. It was tucked neatly next to a rack of other hardware (!!?!!) in a dorm room (!). The guy who's machine it was was insane. He had one machine on which he was trying to set the record for the most OSs on a single box. There was a /. article on this subject a while back but I couldn't find it jsut now for a link. oh well.

    --CTH

    --

    --Got Lists? | Top 95 Star Wars Line
  33. Down but not out... by phatvibez · · Score: 5, Informative
    There are several attempts to resurect the Be Operating System, check out:

    OpenBeos

    OpenBeos is creating a new BeOS from scratch that will be binary compatible with the original BeOS (at first anyway and plan on adding new features that will probably break this later). So far they are coming along at a good pace. They have already created beta's for OpenBFS, Open Media Kits, and their Print Server.

    They are using the NewOS Kernel


    Blue Eyed OS (B.E.O.S)

    Blue Eyed OS is an atempt to bring the Be API and interface to the Linux kernel.


    YellowTab

    YellowTab has some screenshots here: YellowTab Screenshots

    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)
    1. Re:Down but not out... by rasche · · Score: 1

      There are several attempts to resurect the Be Operating System,
      -probably a lot of funerals ahead...

  34. As Barbra Streisand would say, by mtec · · Score: 1


    "To Be or not to Be... um - that's Shakespeare - right?"

    --
    Cake or Death? Cake Please!
  35. When will people learn? by Reality+Master+101 · · Score: 4, Insightful

    The operating system is TOTALLY irrelevent when it comes to most users. There are only three things that matter: 1) Applications, 2) Hardware support, and 3) Applications. You can have the worst operating system in the world (Windows 3.1) and utterly destroy a clearly superior operating system (OS/2) simply because you win the hardware and application battle.

    Be was dead before it started, because the ONLY hope for a new operating system is compatibility with the current application base. What I don't understand is how Be deluded themselves into thinking that application developers are going to spend valuable resources porting to a completely new operating system without any users just because it's "new and cool".

    No one cares about operating systems. Say it three times.

    --
    Sometimes it's best to just let stupid people be stupid.
    1. Re:When will people learn? by KJKHyperion · · Score: 1

      Time for YARP (Yet Another ReactOS Plug)!

      The operating system is TOTALLY irrelevent when it comes to most users. There are only three things that matter: 1) Applications,

      Check.

      2) Hardware support, and

      Check. Sort of :-)

      3) Applications.

      Check ;-) So, do you think that ReactOS can make it?

      --

      Make a difference - use Windows! (open source clone of Windows NT)

    2. Re:When will people learn? by be-fan · · Score: 2

      Um, speak for yourself. If all I cared about was applications and hardware support, then I'd use Windows. But I hate Windows (both using it, and bending over for MS for the opportunity to) so I use Linux, despite the fact that Kopete isn't as good as AIM and I've got no real replacement for Photoshop.

      --
      A deep unwavering belief is a sure sign you're missing something...
    3. Re:When will people learn? by NineNine · · Score: 2

      I think that the original poster was talking about *most* people, not uber-geeks. *Most* people (hell, based on my server logs, I'd say about 99% of 'em) really just don't give a shit. A handful of zealots saying "Hey, we care" doesn't make the broad statement that most people don't care about the OS any less true.

    4. Re:When will people learn? by Joe+Tie. · · Score: 1

      I think that the original poster was talking about *most* people, not uber-geeks. *

      Who knows. He first said most, then changed it to a broad inclusion of everyone on the planet.

      --
      Everything will be taken away from you.
    5. Re:When will people learn? by Howie · · Score: 1

      And you keep the hair-shirt business running too, which is good for them.

      (even the slashdot user called 'be-fan' is advocating Linux over Windows, rather than Be? It really is dead, isn't it? :) )

      --
      "don't fall into the fallacy of believing that Perl can solve social problems. Maybe Perl 6 can, but that's a ways off"
    6. Re:When will people learn? by Dog+and+Pony · · Score: 2

      ReactOS might make it, if it ever catches up. I see some things that need to happen first:

      * It has to work. Currently, those applications and hardware mentioned are on the idea level. :)

      * It should be at least NT5, not NT4.

      * It has to work. See above. How long before it does (and reasonably like w2k?)

    7. Re:When will people learn? by King_TJ · · Score: 2

      Yeah, while I can't really fault you for using whatever makes you happiest and gets the job done -- I honestly think most people take the other route.

      AKA. I hate MS and their pricing, so therefore I run a pirated copy of Windows, and use Linux occasionally (either on another box, as a server - or in dual-boot configuration).

      Who's more "right"? Technically, you are. Which method lets someone get more use of applications from their PC for their dollar though? Umm, I have to go with the guy pirating Windows.

    8. Re:When will people learn? by KJKHyperion · · Score: 1
      It has to work. Currently, those applications and hardware mentioned are on the idea level. :)

      Of course. But on the application side, Wine has already done most of the work. It's the driver support that is very lacking (almost non-existent, primarily because we don't have a full implementation of the registry)

      It should be at least NT5, not NT4.

      Of course. The informations on that page are a bit outdated, our current target is Windows 2000. Since the biggest changes between NT 4 and 5 were on the kernel side (new driver architecture, new driver model), it's another thing that will take quite a bit.

      Unfortunately, we're no Linux, basically no one knows us or cares about us, and the team has as little as 4-5 active members, so things go necessarily slow :-(

      --

      Make a difference - use Windows! (open source clone of Windows NT)

    9. Re:When will people learn? by Art+Tatum · · Score: 1
      What I don't understand is how Be deluded themselves into thinking that application developers are going to spend valuable resources porting to a completely new operating system without any users just because it's "new and cool".

      I think that what *actually* happened was Be deluded themselves into thinking that Apple would buy them and turn BeOS into a next-gen Mac OS. They actually had a shot, but NeXT won that game, thankfully.

    10. Re:When will people learn? by Dog+and+Pony · · Score: 2

      Well then, could you at least please update the page? :) I went there a few months ago, and actually turned away just because it said "NT4" - maybe it still isn't for me, but I had known you were targetting 2000, I'd given it another look at least.

      Something to keep in mind for the future... to gain, and keep, potential users/developers. :)

      Anyhow, good luck with the project. :)

  36. debugging doc ??? by mmu_man · · Score: 1

    What info did you need that you didn't find ?
    between the Anotated BeBook and the Be newsletters... and the source codes...
    Though NIC drivers are maybe the hardest and least documented ones. But as far as debugging goes, BeOS still takes the road, and as far as kernel land is concerned, Linux looses it with it's SysReq key.. The BeOS kernel embeds a full blown debugger. (even with a gdb stub, but Linux has it too IIRC).

  37. well...hundreds of OS's, at the low end.... by Anonymous Coward · · Score: 0

    ...well, I only heard the name before but reading about it it sounds pretty decent, at least a great attempt. Where can you get this on a cheap cd-r, and what is the minimum hardware it will run on? Unfortunately most of my old macs are 68k motorola chips. I will probably leave os 7.x whatever on them things unless ther e is something else that is amazingly better. and really, with no cd drives in them, changing os's is a pain. Will BeOS run on a powerbook 1400? Those are ppc chips, and the older ones, especially the 117 mghz models that no one really wants are fairly inexpensive now. How about old pentium 1's? Those I have a rack of. they have various old versions of windows in stages of decomposition on them. I'd try it I guess if I could get it mailed/shipped for under 10$, downloading is out of the question on rural dialup modem. I'm about ready to order rh 8 and perhaps knoppix to try, might as well try something else as well. Never used any of the bsd's either. I am more interested in OS's that run WELL, keyword there, on older hardware, wqill load in graphical mode with small amounts of ram, as I see a decent "resurrection" niche market in used sales. people who want new computers buy them, a lot of other people want to get a computer for only light use and never had one before. they are looking to drop like 100$ tops for a bundle. At best with a single page printout to take home with them they have to input username, password and isp number to dial and do their own email setup, and that's it, newbies and new experiments are not gonna ever do any command line action, so it has to be simple and work and get on the ole interweb thang, this is millions of people, kids, geezers, etc and for people like me who refurbish to get computers out to people who really can't afford them any other way then near free in cost. Hmm, dumb question, will BeOS run winmodems, which are free usually with these older systems already installed. Can't afford to drop two cents into these bundles, just make them work, with something besides winderz. Recommendations? The redhat is for me personally, I need something for the other boxes I have that does a full install on hard drives less than a gig and not much memory, an EASY install, as I am not a real cli or linux command line guru, and I have to deal with boxes that have between-averages here-8 to 32 megs ram. Just adding ram blows the budget and makes these things unsellable or undoable for donations at my budget, I have to use them as -is, how I get them. thanks.

  38. No doubt by bogie · · Score: 2

    Netpositive was garbage. The first thing anyone did when using beos was download a browser that actually worked with pages written after 1996.
    The thing about old OS's is people tend to remember them with Rose-tinted glasses. BeOs had a lot a major problems with it. Yea it was lightweight, and had a few decent multimedia apps, but beyond that it really didn't have much to offer, and still was missing some major functions like proper networking.

    I think the one thing it will be remembered for mostly is being able to spin a bunch of teapots at once if you happened to own some of the limited hardware it ran on.

    It is funny considering how long ago development stopped on BeOS how the zealots still insist it was the best OS ever.

    --
    If you wanna get rich, you know that payback is a bitch
    1. Re:No doubt by Anonymous Coward · · Score: 0

      Not the teapots, the starflythrough space thingy was so much better. If having a good flythrough space demo was worth something, the BeOS truly was the best ever.

    2. Re:No doubt by Anonymous Coward · · Score: 0
      I think the one thing it will be remembered for mostly is being able to spin a bunch of teapots at once if you happened to own some of the limited hardware it ran on.

      It is funny considering how long ago development stopped on BeOS how the zealots still insist it was the best OS ever.

      It is easy to use. That's the major feature. Linux/Windows even the Mac have problems in this regard. MacOS has lapped BeOS now that ~2 years have gone by since the last release of BeOS.

      Linux/Windows are still doing things that BeOS didn't do. But that's not the point. The point is BeOS is easy to use. Linux/Windows are not. End of discussion.

  39. BeOS Dead - OBOS Alive by Anonymous Coward · · Score: 1, Informative

    Summarizing what everyone said here is basically lack of drivers and apps but otherwise the best OS in history...

    I don't know if you people noticed http://www.openbeos.org ... it's getting closer every day to completion. This time though, it's open source and you can affect in a better way whether your driver will be there or not.

    Apps? Java is on it's way, OpenOffice is there and Mozilla up and running. Someone mentioned Photoshop... Refraction is a clone which is already released.

    BeOS might be dead, OBOS has just started and will succeed where others have failed... // Zoink
    We are United in BeUnited....

    1. Re:BeOS Dead - OBOS Alive by Joe+Tie. · · Score: 1

      Someone mentioned Photoshop

      What somewhat saddens me is just how many BeOS projects are being worked on, and that so many seem to be making progress. What excited me about BeOS back in the day was that companies were just starting to take serious interest in it. I think anything more than one new version of BeOS though will imediatly give the stock reply to Linux development, "Which Linux are we support to write for then?". And that's with products that are pretty much the same aside from some software locations and kernel versions. I personally don't see any chance of something like Photoshop in the present situation of multiple implementations, while back in the day I was quite hopeful for it.

      Ah well, I wish them all luck nonetheless and hope strongly to be proven wrong.

      --
      Everything will be taken away from you.
  40. Never? Hm... by thasmudyan · · Score: 2, Interesting

    I read a lot of posts here saying "Beos would never have succeeded with MS around" or "who had the crappy idea to make yet another OS when there is Linux / BSD?". I don't know if I can leave it at that without some righteous ranting. (Apparently not)

    Beos might be dead but why? In my opinion that happened because a lot of mistakes were made (and creating Beos was none of them):

    1. Be had (and still has) a dead grip on the source code. This is sad, because not only did this scare away opensource guys it was also the main reason for Beos development coming to a stand still. When it was clear (with the economic downturn and blablabla) that Beos couldn't be developed further by one company alone they should have opened the source and a lot of developers would have taken the OS under their wings.
    2. Persistence (or the lack thereof). They thought Beos was going to take over the world over night. When this didn't happen they simply packed and gave up, because Be's business model wasn't stable. If someone had taken a 5 minutes break to think about things they would most likely be among the living companies still. (I don't say this because I am a wise ass who don't know shit about business, because when the IT business was beginning to fall apart I founded an IT company even though the people said "don't do this, it's stupid". It succeeded, it was very difficult at first but we persisted. If you just hold on long enough you will change things!
    3. Partnerships (or the lack thereof). Be wanted to have the cake all for itself. They must have thought that developers and software firms will be grateful just to develop stuff for Beos. This is wrong. They should have made aliances with software companies to roll out tons of apps (Instant Messaging, multimedia, hardware, PIM, a.s.o.). Why the hell didn't they..?

    Sad to see Beos going down, its a great technology. I know I'm going to get flamed for this but when it comes to architecture I prefer Beos over Unix/Linux/BSD/Microsoft anytime.

    1. Re:Never? Hm... by Oliver+Defacszio · · Score: 2, Interesting
      Sigh. Again, I have to listen to how opening the source would have saved (fill in dead technology here). Look, when Be fired up the BeOS, it was for business reasons, not philanthropy. Maybe there were those at glamorous Be headquarters who really did want to offer the world its first Genuinely Good Operating System (c), but I am willing to bet that 95% of the rationale was to make money.

      Thus, when the OS didn't catch on for whichever reason, development stopped. If, say, flat panel TVs never become popular, do you think manufacturers will just throw patents to the wind and idealistically hope that someone else will take up the fight? Obviously not. Even if the magical opening of the source would have saved the OS itself, which I doubt, it would have done nothing to salvage Be and, as a result, wasn't worth the ten minutes required to load source code on the Be FTP servers.

      Sorry to sound like a jerk, but I get so very tired of hearing about opened source is an all-encompassing savior. No, all it means is that you get something for free.

      --

      -
      Inventor of the term 'pardon my French'.
    2. Re:Never? Hm... by thasmudyan · · Score: 1

      Look, when Be fired up the BeOS, it was for business reasons, not philanthropy.
      Certainly not, how on earth do you arrive at that conclusion? When a company starts to open source some of its technology it can make perfect business sense! (Especially if you are operating on a tight budget and cannot really support another, say, 200 man-years of development work per year.)

      Thus, when the OS didn't catch on for whichever reason, development stopped.

      Well, it didn't really have a chance. The management's expectation was that Beos would take over the world within a week or so which was obviously not going to happen. So when Beos didn't replace every damn Win32 machine at the first try they basically gave up (well actually they engaged in a long painful downward spinning self destruction sequence of mismanagement but hey). All I said is that they should have realized that they need help to pull this one (developers, community and industry) and that they shouldn't base their business on a kind of Blitzkrieg model. World class management, bah.

      Sorry to sound like a jerk, but I get so very tired of hearing about opened source is an all-encompassing savior. No, all it means is that you get something for free.

      It might suprise you but I'm not an open source zealot. I develop closed source because I believe it makes sense for the work I got to do. However I strongly believe that you need to open source some software projects in order to achieve something. Starting an operating system from scratch is definetely one such project in my opinion, provided that you aren't MS/IBM or some other giant.

    3. Re:Never? Hm... by Oliver+Defacszio · · Score: 1
      Certainly not, how on earth do you arrive at that conclusion? When a company starts to open source some of its technology it can make perfect business sense!

      Well, I don't claim to follow open-source software very closely, but I can't think of any examples where an open application has ever amounted to a hill of beans economically for the vendor. I am sure it offers some warm-fuzzies morally and can often become the defacto standard (Apache, for one), but how well would Be have been received to open the source, amass the work of happy OSS pundits worldwide, and then close it off and start selling commerical packages? Once open, always open (as I understand the GPL and similar licences), which has shown to be a terrible business model.

      It might suprise you but I'm not an open source zealot. I develop closed source because I believe it makes sense for the work I got to do. However I strongly believe that you need to open source some software projects in order to achieve something. Starting an operating system from scratch is definetely one such project in my opinion, provided that you aren't MS/IBM or some other giant.

      That's not unreasonable, but again, show me how to make money from such an escapade. While you're at it, show RedHat, VA and any number of others, because they sure as hell don't have a clue. What I am saying is that, in this quasi-capitalist world, there's no value in being the good guy by releasing a failing product to the OSS world if it will do nothing to turn business around. Clearly Be was wrong to employ, as you put it, the Blitzkrieg business model, but I don't really see any other options unless one is willing to develop in secret for literally years or has the capital to employ a huge workforce right out of the gate. A tight budget is an instant death-knell to anyone wishing to compete in the business of building an OS.

      --

      -
      Inventor of the term 'pardon my French'.
  41. BeOS may not be dead by michajoe · · Score: 1

    but www.befaqs.com sure is.

  42. not dead by Neotrantor · · Score: 1

    ok.... it's not dead.. think of the original BeOS being like unix and the new obos flavors being like linux. it'll take off, just give it some time

  43. Oh yeah? I can list plenty of dead OS's... by maynard · · Score: 5, Informative
    As a counterpoint to your statement:
    REally, OSes never die, they are essentially immortal, becuase once you find someone who really likes it, they will go to any length to keep the dream alive. Any length.
    So where is RT-11? RSX? Venix? PRIMEOS? CYBER NOS/VE? HP MVS? Lots of operating environments have come and gone... the only systems which remain for the long haul are those with source availability and a developer base able to support the source. This doesn't have to be open source, there are commercial groups who perform this service for a range of defunct products. In fact, many large vertical applications are sold stipulating source availability in the event of vendor bankruptcy. Those systems often stay alive far longer than the vendor ever intended. A good example would be PDP-11s still out in the field controlling tools used in sheet metal factories. It's a dying breed, but they're still out there -- and they're only dying because LSI-11 cards on the used market are getting hard to find.

    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

  44. AmigaDOS was not designed to be "Unix-like" by msobkow · · Score: 2

    AmigaDOS was actually created as a masters thesis project in operating systems at a university in England, IIRC (it could have been a different country.)

    It did not have Unix-style commands, APIs, or underpinnings. There were a lot of add-on programs created to give it shell-like functionality, and it supported ideas like process parentage and priorities, but no one who has ever done systems programming on a *nix system would confuse it with a *nix core.

    The Amiga died due to Commodore's pathetic marketing. Period.

    --
    I do not fail; I succeed at finding out what does not work.
    1. Re:AmigaDOS was not designed to be "Unix-like" by Anonymous Coward · · Score: 0

      Amigados was purchased at the last minute after the (nameless) vendor tho was supposed to provide the O/S backed out (the failed project was the Commodore Amiga Operating System, CAOS). I think the version released was Tripos based, producd by MetaComo (somehow I thoght Helios software was also related). Interestingly, it was not implemented in a "normal" programming language, but used BCPL.

    2. Re:AmigaDOS was not designed to be "Unix-like" by Anonymous Coward · · Score: 0

      Is it really that long ago that everyone has forgotten?

      The shell was an integral part of the OS. It came in the ROM, for crying out loud...

      As for your assessment of the cause of death, I agree 100%.

  45. Dead? by amdg · · Score: 4, Funny

    Customer: 'Ello, I wish to register a complaint.
    (The owner does not respond.)
    C: 'Ello, Miss?
    Owner: What do you mean "miss"?
    C: I'm sorry, I have a cold. I wish to make a complaint!
    O: We're closin' for lunch.
    C: Never mind that, my lad. I wish to complain about this OS what I purchased not half an hour ago from this very boutique.
    O: Oh yes, the, uh, the BeOS...What's,uh...What's wrong with it?
    C: I'll tell you what's wrong with it, my lad. 'E's dead, that's what's wrong with it!
    O: No, no, 'e's uh,...he's resting.
    C: Look, matey, I know a dead OS when I see one, and I'm looking at one right now.
    O: No no he's not dead, he's, he's restin'! Remarkable OS, the BeOS, idn'it, ay? Beautiful GUI!
    C: The GUI don't enter into it. It's stone dead.
    O: Nononono, no, no! 'E's resting!

  46. I'm not dead yet! by antiher0 · · Score: 1

    You'll be stone dead in a moment!

  47. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  48. Mirrror anyone? by Anonymous Coward · · Score: 0

    Would someone post a mirror site? /. effect makes the article unavailable.

  49. BeOS is why I'm using OS X by bedouin · · Score: 4, Interesting

    BeOS really prompted me to start exploring other operating systems. Before that I had toyed with Linux once or twice, but it never worked quite the way I was hoping to. I started hearing some buzz about BeOS and actually /bought/ r4.5.2, along with the BeOS Bible. This was one of the only pieces of software I /paid/ for (as opposed to warezed) since maybe DOS 6.0.

    I was fortunate enough to have an external USR modem, as well as a VooDoo 3 graphics card; no problem with compatibility, in fact I had the perfect system. Aside from the OS being incredibly fast, it more or less worked the way it was supposed to. I also thought the GUI combined the best of both Windows and MacOS. For those that say it lacked applications, that's true - but at the time it wasn't really any worse than running Linux. There was a decent office suite, Opera for a Net+ replacement, and a couple different mail apps to choose from. I can't remember which one I settled for, but I remember using a hex editor to remove its unregistered tagline :). BeOS was not a server OS, but ruled on the desktop.

    As Be the corporation started dying, I was seeing less and less work put into the OS. In r5 Pro OpenGL support had been removed for some reason, and to my knowledge never returned. It started to become clear that the OS was seeing its last days, and I didn't really want to be like the Amiga zealots who still exist today, so I went searched for some alternatives.

    The thing is, using Be showed me that using my computer could be kind of fun again; maybe not fun, but at least enjoyable. I started toying with Linux on an old Pentium box, only with the intention to make it into a firewall for the box that was running Windows and Be (since Be had no firewall). Eventually this led me to install Redhat 6.2 on another partition on my main workstation (the box running Be), and I was using Linux as my primary OS for maybe a year or two.

    Meanwhile, I was toying around with the old Pentium firewall more and more, and making it do some really great things under Linux - as a server. On the other hand, getting day to day tasks done in Linux on my workstation box was a new issue every day. I kept Linux running on my server (where it's still running) and axed both Linux and Be on my workstation, opting instead to Windows 2000 Pro. I hated how Windows looked and felt, and didn't much like the company who made it - but things more or less worked . . . at least for six months or so, then something breaks for some reason and a format is necessary.

    Last year I acquired an old Macintosh Quadra 700 with OpenBSD on it. This little Mac, alongside the interest I already had in OS X, really nudged me even closer to putting down the money for a Power Mac G4, and so I did this May. OS X is most of the things I loved in BeOS (a nice, logical GUI) and consistency (it generally does not require reinstallation after 6 months, for no reason at all). At the same time, it fills the gaps that Linux did. It's UNIX, and works nicely alongside my BSD and Redhat boxes; when I'm not sure how to do something the 'Apple way' I can just open up a terminal and do it the way I would on any other UNIX box. On the more evil side, Office and Photoshop are there, so I don't have to reboot just to get something done. And if worse comes to absolute worst, Virtual PC can be used for any Windows-only app I might encounter (but it hasn't really occurred yet).

    1. Re:BeOS is why I'm using OS X by NineNine · · Score: 1

      I just love it when a random person decides to post his own personal autobiography on Slashdot. Nobody really gives a shit unless you're somebody important or interesting or at the very least marginally famous. I mean really, should I post my personal history of footwear?

    2. Re:BeOS is why I'm using OS X by Anonymous Coward · · Score: 0

      Maybe he is marginally famous.

    3. Re:BeOS is why I'm using OS X by Ieyasu · · Score: 1

      Oh please. This is one of the most well-written posts I have encountered on /. in a long time. The positive moderation is worth it for that alone.

  50. Why are you so surprised they abandoned it? by fmaxwell · · Score: 5, Interesting

    To this day I'm suprised they abandoned the hardware business so quickly.

    While I loved BeOS as an OS, I hated Be, Inc. as a company. They abandoned every product and customer that they ever had. They abandoned the BeBox hardware and even stopped supporting it in later revs of the OS. They abandoned the Mac users that ran BeOS on Macs. They abandoned BeOS users and developers to pursue the (idiotic) network appliance market. Not surprisingly, the network appliance makers were not eager to jump into bed with a company that might abandon them next.

    Be was a perfect example of what happens, and what should happen, to a company that abandons its customers and supporters.

    1. Re:Why are you so surprised they abandoned it? by Maniakes · · Score: 5, Informative
      They abandoned the BeBox hardware and even stopped supporting it in later revs of the OS.

      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.

      Compaq repeatedly assured Be of its enthusiasm for the project, and stated that only BeOS could meet the project's technical, cost, and delivery timeline requirements. Compaq assured Be that Windows CE was not suitable for the device.

      In October 1998, however, Compaq informed Be that it had disclosed information about the Be Internet appliance project to Microsoft. Later that same month, Microsoft Chairman Bill Gates visited Compaq CEO Eckhard Pfeiffer as part of a "Digital Appliances Review."

      In early November, under pressure from Microsoft, Compaq informed Be that it was no longer interested in licensing BeOS.

      --
      A legparnasom tele van angolnaval.
    2. Re:Why are you so surprised they abandoned it? by truenoir · · Score: 1

      Be didn't abandon Apple, Apple denied them access to the G3 motherboard information they needed to port the OS to it. Actually, I think the G3 processor information was needed, as upgrade cards weren't even supported.

      It was a shame though, that Be just didn't seem to have the ability to do anything right except the OS...

    3. Re:Why are you so surprised they abandoned it? by entrylevel · · Score: 1

      Why is it that Be couldn't be ported to G3s or G4s, but every other Linux and *BSD kernel could?

      --
      Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
    4. Re:Why are you so surprised they abandoned it? by andrewski · · Score: 1

      Don't get mad at Be, Inc. A lot of folks who worked there are as pissed off as you are about the state of things. The whole problem can be traced back to one French fuckhead - Gasse. He is a stone cold bitch. He is the person who drilled Be into the ground, as it wasn't turning profit fast enough for him. As a sidebar, he just got fired from his new job, may he rot in hell.

    5. Re:Why are you so surprised they abandoned it? by snarfer · · Score: 1

      While I largely agree with you, Be did not abandon Mac users, Apple forced that by refusing to work with Be.

    6. Re:Why are you so surprised they abandoned it? by Anonymous Coward · · Score: 0

      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.

      No you weren't. You were not selling BeOS. You were not advertising it, not supporting your developers, and you had a grand total of one person in the company whose job was selling BeOS. Even with that I'm told sales were more than doubling every quarter.

    7. Re:Why are you so surprised they abandoned it? by fmaxwell · · Score: 3, Interesting
      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.

      The BeBox platform was not even mentioned in the BeOS Pro Edition 5.0 User's Guide the documentation, so I don't know what kind of internal testing was done, but if there was support for the BeBox, it was well-hidden.

      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.

      But Linux was ported to it by a people working in their spare time.

      That was a last ditch effort to survive.

      And it was transparent to BeOS customers and vendors alike.

      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.

      But still Be continued to lie to BeOS 5.0 purchasers. One need not have looked any further than the "Registered BeOS User Area" for proof that Be, Inc. had no interest in supporting BeOS customers. Months and months went by and there was never anything released via that worthless page. No drivers for new hardware. No updates or new software. Nothing. On the page, users found the lie "we will be adding additional features in the near future." The new networking layer, BONE, was never released. The OpenGL support was never released. Updates for new hardware never appeared.

      Third-party Be developers were also left hung out to dry. like Wildcard Design and Thunder Munchkin Software close their doors, horribly in debt and sometimes in legal trouble, due to the conscious decision by Be, Inc. to abandon them. I thought that the following excerpt from a letter by Todd C. Brett, CEO of Thunder Munchkin Software, summed up the situation well:

      Developer services have been reduced to highly expensive support for large corporations or consulting firms (with a noted preference for web appliances), leaving developer support for mainstream applications all but dried up. Simply trying to communicate with important staff to ensure quality service to our customers, let alone actually getting something done with Be, Inc., has become an unbelievably painful experience. The message made to small pioneering BeOS companies such as ours has been made crystal
      clear: we are not needed anymore.


      Perhaps, but several (including Compaq) did sign on to use BeIA, only to switch to WinCE under threats from microsoft.

      And others, like Netpliance, went with OSs like QNX. Was Be actually surprised that Microsoft pressured companies like Compaq to use WinCE? This is the same company that sabotaged Digital Research's DR-DOS by purposely making Windows beta installs fail with vague claims about (non-existent) compatability problems.

      Of course, all of this is just a moot point. As I predicted in my e-mail to JLG, the Internet appliance market was a non-starter and, even had every vendor of those devices used BeIA, it would have made little difference. It's just a shame that Be could no go out of business on a high-note, supporting their loyal customers and developers to the end.
    8. Re:Why are you so surprised they abandoned it? by Maniakes · · Score: 1

      But Linux was ported to it [the G4] by a people working in their spare time.

      People didn't work on BeOS in their spare time. Linux had (and has) far more developer resources than Be ever did. At our peak, Be had ~20 programmers, several of whom were working on apps, not the OS itself.

      --
      A legparnasom tele van angolnaval.
    9. Re:Why are you so surprised they abandoned it? by FyRE666 · · Score: 3, Informative

      In early November, under pressure from Microsoft, Compaq informed Be that it was no longer interested in licensing BeOS.

      Until late last year I was working with a team using the Compaq "Clipper" devices running BeIA on a B2B project. While I'm no MS fan, in fact quite the opposite, I'm sure the pressure from the Beast of Redmond wasn't the only reason for the switch.

      The BeIA OS, while impressive had serious bugs until the point we abandoned it. Calls and emails to Be went unreturned for months on end, and updates to fix bugs were few and far between. The main problem (or one of them) that we had was with the Opera browser and OS constantly leaking memory until the device would reset - losing any information in other apps. This meant having to add code to constantly save state to the flash RAM, severely shortening its life.

      Curiously the browser would crash after loading 15-20 pages, then be killed and restart, but the user would be oblivious to this, since if it was running fullscreen (the default, and only option on a locked machine) then the old image of the browser would stay in the display buffer, then replaced when the browser restarted - which I thought was a cool trick!

      It was far more suitable than WinCE, there's no doubt about that, but QNX was probably a more efficient system still...

    10. Re:Why are you so surprised they abandoned it? by Maniakes · · Score: 1


      The BeIA OS, while impressive had serious bugs until the point we abandoned it. Calls and emails to Be went unreturned for months on end, and updates to fix bugs were few and far between.


      Now that I think about it, this doesn't surprise me The already-too-small development team was split between BeIA, the Opera port, and BeOS R6. On top of this, many of the best people were leaving because they expected the company to fail, and they weren't being replaced because the money wasn't there.

      --
      A legparnasom tele van angolnaval.
    11. Re:Why are you so surprised they abandoned it? by themurray · · Score: 1

      It was a shame, since BeOS had much hope for the future on PCs at least. I did like 4.5 and even tried the 5 free release.

      BTW, Compaq needs to learn to grow balls like every other tech company. Microsoft is only as powerful as you let it be, since they are not the only supplier of the OSes. Just everyone made the mistake of falling into that rut!

    12. Re:Why are you so surprised they abandoned it? by Anonymous Coward · · Score: 0

      So by your stats they have been losing $20 million on $4 million revenue? What's your point?

    13. Re:Why are you so surprised they abandoned it? by burnetd · · Score: 1

      Be Inc was a company, and could be sued. Although Be probably would have won the law suit the cost of fighting it would have took them under.

    14. Re:Why are you so surprised they abandoned it? by Art+Tatum · · Score: 1

      Be was the NeXT of the 90s. Great technology, bad business decisions, terrible marketing, and consumer lock-in killed Be and severely wounded NeXT.

  51. OpenBeOS: not here now, alternatives available... by maynard · · Score: 3, Insightful

    First of all, I'm not in the naysayers camp about OpenBeOS. If developers want to rewrite BeOS to scratch their own personal itch, far be it from me to tell others how to spend their personal time. However, OpenBeOS is not ready now. Yet for a vendor targeting a vertical market there are so many other available platforms to choose from now, that waiting (or even developing) for OpenBeOS simply doesn't make sense. These guys are in business to make money, not to scratch a personal development itch. If that's the market I wanted to target I would likely choose either Windows or Linux, depending on how I wanted to price my product, and how I wanted to arrange support. I might even go QT and target both platforms. The last thing I would do is hope and pray for OpenBeOS to come along and save my day when the market was there for the plucking and alternatives to OpenBeOS readily available. Just my .02...

    Cheers,
    --Maynard

  52. site running on BeOS/BeBox? by khuber · · Score: 1
    Someone'd better check on the server - I think the GeekPort is leaking!

    -Kevin

  53. so you are saying... by Anonymous Coward · · Score: 0

    so you are saying that, in the best traditions of "business sense" they ran it into the ground with bad decision after bad decision, yet not opening it would have been another bad decision? To me it looks like sour grapes on Be's part, or somehow the ceo needed a vist from his employees and stockholders all holding baseball bats or something. Really, people are too afraid to "confront the boss" or something. This is (one reason of many) why unions started. IT people need unions. I bet a million of them laid off in the past few years might be thinking on this now. and maybe the same million might now understand that half a decent salary is better than zero salary, and perhpas they had an ego problem with payscale and worth as well, considering they know this is a world economy now, like it or not, that decision is out of our hands for the moment with this crop of politicians and globalists.

    Never used it might have liked to try it from the sounds of it. I understand from this thread there is an open source effort but it's completely diofferent-hmm, sort of defeats the purpose, sort of like calling your new car company ferrariopen, but it has no ferrari there. Oh well, I don't profess to understand business other than watching my boss right now go down the tubes from bad decision after bad decision, yet he won't take any advice from anyone else because "he know's what he is doing". Too bad it effects so many other people, he's paying for his ego trip to the tune of..well, lotsa moolah. Maybe that happened to BE as well, I don't know. it sure seems to be happening to the US in general where the current 'approved" business model is to export as many jobs as possible overseas in the magical outlook that they will keep the same number of customers, as employee after employee in the US becomes a non-buying person as they have *no* work.

    1. Re:so you are saying... by thasmudyan · · Score: 1

      so you are saying that, in the best traditions of "business sense" they ran it into the ground with bad decision after bad decision, yet not opening it would have been another bad decision? To me it looks like sour grapes on Be's part, or somehow the ceo needed a vist from his employees and stockholders all holding baseball bats or something.

      AC, I absolutely agree. As I wrote, the entire Be business plan was flawed and based on false expectations and wrong decisions. I didn't say in any way (as Oliver Defacszio would have it) that open source is the saviour for any project nor did I say that Be should have been a philantropic organization. All I meant is that there have been a lot of stupid decisions and opening the source to get broader support would probably have helped a lot to keep the project alive. Also, read my previous post again, this time not only that one sentence, as there were other points in it besides the (granted) stale open source statements.

  54. BeOS is not dead, Not close to dead by Anonymous Coward · · Score: 0

    It's not even close to heavy breathing. Someone showed off this years IA offerings, and I stated "we did that". As a server OS? Only time to get better at that, and there is major work underway to make things possible like distrubuted clustering, massive paralellism, hardware accel opengl and other functionalities. BeOS is only one of a small handfull of OS's with it's own office
    suite (Read: GoBe Productive), and that will see continued development. It's not obscure, or as obscure as many OS's out there, although it's presumed by some to somehow be non viable for one use or another.

    We have a lot of people working on the project to restore the operating system, and bring it to a clean maintainable status at the OS level. In addition to OS related projects, and the projects I mentioned, there is Java2 in the works, open office in the works, and countless deep development projects, some of which you just don't know about, as it appears that sometimes things get worked on by people in the community who are not accustomed to telling people about what they are doing until it's done.

    We have some increadable 3d and CAD modelers coming down the pike, multimedia applications of all kinds and other special projects.

    So, the OS isn't dead, it's not even smelling. It's the most exciting "third party" on the planet!

  55. why BeOS was fast for awhile by linuxislandsucks · · Score: 1

    for those who have seem to forgotten BeOS orginally was not multiuser.. so yes of course it booted faster than some dos and mac systems..duh!

    But BeOS needed to be multi-user and a year or so after Steve Jobs turned down an offer to buy BeOS.. finally one forme Apple Exec Jean G..finally got his head out of his butt..but I digress..

    --
    Don't Tread on OpenSource
    1. Re:why BeOS was fast for awhile by Anonymous Coward · · Score: 0

      um... yeah... uh... sure... ok...

  56. Re:Oh yeah? I can list plenty of dead OS's... by dispensa · · Score: 1

    The key distinction here is that those are server OSes. The poster was referring to that thing that's actually running on your computer, that you type directly into on a daily basis. Linux, Amiga, Be, Mac (with sub-zealout categories including OS 9 and OS X), and Linux (KDE, Gnome, WindowMaker, Enlightenment, twm :-) and so on).

  57. Not BeOS, but close by Anonymous Coward · · Score: 0

    You might want to take a look at Syllable Although it isn't BeOS, it is a continuation of AtheOS, and has that same BeOS feel to it. 0.4.2 has just been released, and its quite mature and usable.

    1. Re:Not BeOS, but close by Anonymous Coward · · Score: 0

      Try again (Slashdot needs an "Edit this post" button)...Syllable There.

    2. Re:Not BeOS, but close by phatvibez · · Score: 1

      I agree, I have been watching AtheOS, and now Syllable, for a while and it looks promising!

      especially when looking at this...

      Daryl Dudely's new preference apps

      and now they even have samba compiled for it Here!

      I even have a link to them on my website so that I can easily check out any new updates.

      --
      --- Brad (http://www.LinuxReview.net)
  58. There was plenty of software for be by t0qer · · Score: 2

    People are making me mad saying there wasn't any decent software on be, bullcrap.

    All that killed Be was crappy hardware support.When Be came out, it supported about 5 or 6 network cards from 2 manufacturers (3com and intel) 1 scsi adapter from adaptec, and 3d support was mostly written for the 3dfx chipset. Why wouldn't they support a adaptec 29160??? Pretty standard stuff if you ask me.

    Be 5 they added a little more hardware support, but again it was very limited.

    Now back to my original bitch about people bitching there was no software.

    Be had word processors, (and excellent printer support, sort of a oxymoron compared to the rest of their hardware support)
    Be had (has) some of the best console and arcade emulation support EVER! Mame games that take a 700mhz cpu in dos can do just as good with a 350.
    Their sound editing tools were the best, Be's sound drivers concentrated on low latency which meant the real time effects processing on be kicked ass.

    As far as M$ killing be, well M$ did tell OEMS you beos no windows. Lets not forget palm though, who bought it all out and has kept all the source for their palm os sort of like a junkyard parting out a car (sad to see it end like that) The palm thing is kinda sad because it forever dooms Be to run on slow hardware.

    All in all though, be was excellent. My band uses it on a 200mhz pentium for recording jam sessions and it works great. Only 2 ppl in our band are computer savvy and Be is simple enough where the other guys can sit down and use it.

    Well enough ranting about the whole be fiasco for today...it's sunday, time to pray to a dead god.

    1. Re:There was plenty of software for be by sql*kitten · · Score: 2

      All that killed Be was crappy hardware support.

      If the BeOS had applications that could do something useful (where "useful" is defined as "commercially valueable") then that wouldn't have mattered, because people would have bought BeBoxes. That's exactly how Apple ran their business in the early days: customers bought the application (in that case, DTP) and bought the hardware specifically to run it. Do people buy Macs because of Photoshop or vice versa? To many Apple customers, their computers are simply image-manipulation tools, the applications are all that matters and the OS is just the plumbing.

      A company will find an application that does what it wants and then buy the infrastructure to run it, not the other way around. (I have seen this many times in the engineering and finance industries). A savvy consumer will do the same.

      Be had word processors, (and excellent printer support, sort of a oxymoron compared to the rest of their hardware support)
      Be had (has) some of the best console and arcade emulation support EVER! Mame games that take a 700mhz cpu in dos can do just as good with a 350.
      Their sound editing tools were the best, Be's sound drivers concentrated on low latency which meant the real time effects processing on be kicked ass.


      Can it do any of that an order of magnitude better than the other products on the market? Word processing is a solved problem, you can get high quality word processors on any platform. Playing emulated games is fun, but there's no money to be made there, and what Be needed most of all was money. And sound editing is another application-centered business, if Be wasn't running Cubase (or whatever) it couldn't even compete.

  59. Lawsuit by dispensa · · Score: 2, Interesting

    What ever happened to that lawsuit Be had against microsoft over anti-trust issues? Last I checked (a month or two ago), they were continuing to run the corp for the purpose of pursuing litigation. Read the dissolution statement on the website - it goes out of its way to preserve the right of the Be shareholders to file lawsuits.

    I'll betcha there's something in the works, otherwise they wouldn't have spent the time keeping the corp running.

    1. Re:Lawsuit by Rude+Turnip · · Score: 1

      It's still happening. The last press release was in August saying that the venue was changed to Maryland. The ticker symbol for Be, Inc. is now "BEOSZ" if you want to track the headlines.

    2. Re:Lawsuit by Shalome · · Score: 2

      I worked with Donovan Schulteis, the guy who wrote Be's briefing in the MS antitrust trial. As far as I know, all that happened was the brief was filed as evidence to be reviewed by the court.

      *shrug* He's working with [url=www.beunited.org]BeUnited[/url] now.

      --
      Moderation totals that amuse me for one of my posts: Flamebait=1, Insightful=2, Funny=2, Overrated=1, Underrated=1
  60. That's funny.... by maynard · · Score: 1

    I seem to remember RT-11 as a single user platform... can't really call it a desktop box since even the lowest end PDP-11/03 fit in a half-hight 36u rack, but dishwasher box might be an apt description... (and shall I bring up Xerox Altos as yet further evidence that your position is unsubstantiated by the facts?) --M

    1. Re:That's funny.... by dispensa · · Score: 1

      Are you saying that you disagree with the basic premise that most of the dead OSes are basically server OSes? Or that most workstation OSes that attained reasonable market success are still being supported or re-implemented?

      People are willing and able to port server apps / daemons / etc from platform to platform, but the fundamental way of interaction with the computer is trickier to port from OS to OS. Also, end-user apps tend to be more tied to an OS than daemons.

    2. Re:That's funny.... by Anonymous Coward · · Score: 0

      You don't use your Alto anymore?

  61. death by greed by peter303 · · Score: 2

    Apple approached Gassee before Jobs looking for a software rescue of Apple. Gassee wanted an even billion while Jobs settled for $400M (and eventual takeover of Apple). Apple OS X could have BeOS instead of NeXT-Unix.

  62. One processor per person _is_ enough by jncook · · Score: 5, Informative

    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.

    1. Re:One processor per person _is_ enough by bnenning · · Score: 2
      But a MacOS X-class OS would have shipped four years earlier, and had outstanding multiprocessor support in the core.


      Doubtful. Apple would have had to integrate existing Mac OS technologies (QuickTime, Java, AppleScript, etc) and create a Carbon-style compatibility layer for BeOS the same way they did for OpenStep. It probably wouldn't have taken any less time, and they would have ended up with a not-quite-Unix system and an API that, while good, doesn't compare to Cocoa.

      --
      How to solve most of our problems: 1.Lots of nuclear plants. 2.Cure aging.
    2. Re:One processor per person _is_ enough by jncook · · Score: 1

      Perhaps. In 1997 fredlabs (www.fredlabs.com) demonstrated VirtualMac, which enabled System 7 applications to run in a compatibility layer. I played with it several times, running then-crash-notorious Microsoft Word, Excel and the like without difficulty. It was written, I believe, by two guys named Fred, one of whom was an ex-Apple employee who worked on their 68k emulation engine for PowerPC.

      With this technology (and a fair amount of compatibility testing) Apple could have had many Mac applications up and running on the date of purchase. With NeXT they had to write the compatibility layer themselves from scratch. This put Mac developers in limbo while it was written. With Be, the current crop of MacOS applications would have continued to run while developers explored the new API.

      While Be did not have a complete QuickTime implementation, without access to source they were able to cobble together enough codec support to play movies. With source they probably could have done much better. And in 1997 all the bells and whistles of QuickTime were less important than just playing audio and video.

      Java eventually came to BeOS as part of the several browser projects.

      AppleScript would undoubtably have been replaced outside of a compatibility environment. Be supported copy/paste, drag-and-drop, and interapplication communication (all really the same thing if designed properly) with BeMessages, multi-part, typed, intra- and inter-application message packets. These could be generated from any scripting system, or from the command line. (Remember 'tell'? As in, 'tell terminal BeQuit'?) I believe someone wrote or was working on a system to transport these across a network. But basically, you could inject messages into any application's message processing queue, which made most applications scriptable for free.

    3. Re:One processor per person _is_ enough by hyeh · · Score: 1

      I don't think it was the emulation engine that delayed OS X. After all, Apple has had tremendous Mac-on-UNIX experience with MAE for HP/UX and the System 7 layer on A/UX.

      Also, people must remember that Mac OS X Server was released nearly a year before OS X consumer. Therefore, I believe the hold up was due to introduction of Aqua into the mix (and writing device drivers).

  63. Re:Oh yeah? I can list plenty of dead OS's... by RedneckTek · · Score: 1
    So where is PRIMEOS?

    The last company I worked for used Prime. OF course, they're gone (absorbed into another division), but from what I understand the Prime is still running in case they need any data from it. They're afraid to shut it off, because it might not come back up. So I guess that OS will live forever, or at least until a hardware failure.

    --
    I gave up thinking of a cool sig
  64. Nope. by maynard · · Score: 1

    Are you saying that you disagree with the basic premise that most of the dead OSes are basically server OSes? Or that most workstation OSes that attained reasonable market success are still being supported or re-implemented?

    Neither. I originally pointed out a variety of OS environments which have died throughout the years to refute the claims of the top level post in this thread. The list I posted is a small subset of the entire history. Your argument that I listed only server OSs is incorrect simply because I listed one OS which by definition could never have been a server. Then I pointed to a graphical desktop OS that was intended as an early desktop which is now completely dead, to nail the point in further. Finally, I now point out that since I only listed a small subset of the total I bet one could easily find further examples beyond BeOS of completely dead desktop operating systems. Hmmm: CP/M, NEWDOS/80, OS9, TOS, CP/M (oh, so many more)... just off the top of my head.

    As an aside, I note that many of the other OSs I listed were not "server" systems in the modern sense of the word because they were traditionally installed as multiuser minis or mainframes with a number of serial terminals hung off them. This was long before networking became common. But I would agree the distinction is blurred. Another point I would make is that many of these environments didn't really share the philosophical development background of 'NIX, so the APIs and system environments were totally different. For example, a port from HP MVS to HP-UX could be a significant task given the large differences between the two platforms. Though we appear to largely agree on this.

    Cheers,
    --Maynard

    1. Re:Nope. by MrBoring · · Score: 1

      Minor point: MVS is made by IBM, not HP, became called OS/390 and now is called z/OS.

  65. Heh... by Anonymous Coward · · Score: 0

    nice anecdote. :)

  66. MODS: Please mod parent (by Maniakes) up.. by ABetterMan · · Score: 1

    Parent is an informative post about the demise of BeOS, from an apparent ex-employee. Please mod it up. :)

    --

    Someone you trust is one of us.
  67. Quick or correct. by Inoshiro · · Score: 2

    Pick one.

    I pick correct, because I like having things done right the first time. It reduces the amount of crap I have to put up with.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  68. ...It Never Dies a Natural Death by Anonymous Coward · · Score: 0

    An operating system never dies a natural death.
    It dies because we don't know how to replenish its source.
    It dies of blindness and errors and betrayals.
    It dies of illness and wounds;
    It dies of weariness, of witherings, of tarnishings.

    (Anais Nin)

    PS: OK, she originally spoke about a similar emotional topic (find it out :).
    But her poem matches quite well, don't you think?...

  69. Comment removed by account_deleted · · Score: 2

    Comment removed based on user account deletion

  70. Dead? by skahshah · · Score: 1

    If BeOS is dead, then I have a pretty efficient zombie hiding in my machine!

  71. BeOS has it's uses by BlameFate · · Score: 1
    You know, I invested in a Mac for OS X last year, and it's now my primary platform, and encouraged me to mess about with operating systems so much, that I am looking in to going totally windows free on all my machines.

    Ultimately I want to go Linux, but I am having a heck of a time deciding on a simple distro for my 'lil 4-year old laptop AMD K6-266 w/ 3-gig HD. All I want is a really thin net client really. I have tried Debian; but I am too much of a newbie to be able to get it working - whilst learning that however; I've thrown BeOS on it just this very evening; got the pcmcia network card talking to the OS, and am posting from it now - I'ts a little gem of an OS and seems very bloat free. Love the GUI too.

    All I got to do now is learn how to configure me a linux install reasonably like this!

    N.B. No, I'm not a 13 year old new to computing, just new to OS exploration.

    --

    --is not to be confused with user #672982 - Bame Flait

  72. BeOS 5 PE Max Edition V2 by darkxman · · Score: 3, Informative

    something new to play with...
    http://www.vasper.net/main.php

    BeOS 5 PE Max Edition V2 Release Notes
    http://www.vasper.net/rnotes2.htm

  73. to go down in history by RestiffBard · · Score: 3

    I admire the openbeos people. i hope they succeed in making a viable beos that I can run.

    unfortunately I'm afraid beos will, like os/2, go down as being the os we wished that was.

    I've used os/2 and beos and at least 30 other OSs and those two I miss most of all.

    --
    - /* dead coders leave no comments */
  74. BeOS isn't dead by Nailer · · Score: 2

    It either:
    a) lives on in its music
    b) Works at the local 7/11 with Elvis and Osama

  75. RT-11 is here by g4dget · · Score: 2
    RT-11 is here:

    http://simh.trailing-edge.com/.

    However, if it's not open sourced, obviously, it can't evolve much further, so in that sense, operating systems do die.

  76. threading and typing in Linux by g4dget · · Score: 2
    My 2 GHz P4 running KDE 3.x (Gentoo, uber-tricked out) still doesn't match the responsiveness of my 300 MHz PII running BeOS (dead stock, no tweeking), though its getting close thanks to 6x the processor and 10x the RAM.

    Linux doesn't try to optimize interactive responsiveness--and most of its users wouldn't want it to. Linux aims for having a compromise between good interactive performance, good batch performance, and good multiuser performance.

    However, with the new kernel thread implementation (run 100000 threads if you like) and the preemptible kernel, I suspect that Linux actually would match BeOS if you chose to configure it that way.

    BeOS stored the MIME type of a file in an attribute

    The designers of UNIX chose 25 years ago to keep the file system as simple as possible, and their choice has proven to be the right one for UNIX and Linux applications. If you want something like an attributed file system under UNIX, you stick the content and the attributes together into a directory; a UI can treat the directory as a single entity. That's what Mac OS X does, and it works very well.

    For files in particular, file type identification based on fingerprints, as used in UNIX, is more robust and, if anything, simpler from the application programmer's point of view.

    1. Re:threading and typing in Linux by be-fan · · Score: 3, Informative

      1) It's not whether or not the Linux system can technically handle all the threads. It can and has been able to for years now. The problem is that Linux GUI applications are not written in such a way that emphasises interactive performance. And there doesn't have to be that much optimization for it. The BeOS (and Windows to a large extent) kernels "optimize" for interactive performance in the sense that they offer a standard priority scheduler. The GUI itself then uses this to set the priority of GUI apps high by default. The same effect can be achieved in Linux by manually renicing X and your apps (or in the case of a DE, the gnome-session or startkde processes).

      2) Sticking attributes in a directory is a bad idea. Giampalo, in his book about the Be file system., talks about how that was his original implementation (each file has an associated atttribute directory) but the GUI's need to access several attributes (timestamps, filetypes, etc) for each file necessitated including a shortcut mechanism at least for certain small attributes. And attributes are a *good* idea. Moving forward, both XFS and Reiser4 will have them, and Linux will support them through a common API. As for filetyping, UNIX's "fingerprint" mechanism is only half a solution. Most files have no detectable fingerprint and this will only become more common as more text-based formats (XML) proliferate. BeOS includes a registrar daemon that uses file fingerprinting to recognize files and attach to them an attribute identifying the type. These attributes can be edited by the user for increased flexibility.

      --
      A deep unwavering belief is a sure sign you're missing something...
    2. Re:threading and typing in Linux by g4dget · · Score: 2
      Sticking attributes in a directory is a bad idea. Giampalo, in his book about the Be file system. [...] his original implementation (each file has an associated atttribute directory)

      Well, no wonder that he wasn't satisfied with that: that's a lousy implementation because the two can become disassociated. A better implementation is to stick both the content and the attributes into a single directory and treat the directory itself as a single document in the GUI.

      For my day job, I work with millions of files, each having dozens of attributes. A set of special-purpose APIs would be an enormous headache. I run into this occasionally when I use platforms that do have attributes.

      Linux will support [attributes] through a common API

      A lot of junk has been dumped into Linux, much of it not very widely used. If the majority of Linux software ever started relying on such features, Linux would cease to be a UNIX-style operating system. UNIX was designed by people rebelling against nonsense like ACLs, file attributes, etc.; it was a deliberate choice.

      Most files have no detectable fingerprint and this will only become more common as more text-based formats (XML) proliferate.

      XML files are supposed to identify what the XML represents. Dumping bits of XML into a file and determining its type through file attributes is contrary to everything XML stands for. Other text files encode their type as part of their file name (usually, an extension).

    3. Re:threading and typing in Linux by be-fan · · Score: 2

      Well, no wonder that he wasn't satisfied with that: that's a lousy implementation because the two can become disassociated.
      >>>>
      You didn't even understand the implementation. Who cares about your opinion of it? The directory was to be a hidden one accessed through a pointer in the inode of the given file. There is no way the two could become disassociated.

      A better implementation is to stick both the content and the attributes into a single directory and treat the directory itself as a single document in the GUI.
      >>>>
      The problem with the orignal implementation was not disassociation, but performance. Instead of taking one disk access to display a file, it took several. That killed the speed of the file browser. And your implementation is really annoying to the user. I really hate OS X in the way it represents things differently in the GUI than in the actual OS. What if you don't use the GUI for file browsing? You go and modify bash to handle the hack too? With the attribute implementation, the only tools that need modification are those that deal with directories directly. It is much closer to the standard UNIX file semantics and the user's idea of what a file is.

      A lot of junk has been dumped into Linux, much of it not very widely used. If the majority of Linux software ever started relying on such features, Linux would cease to be a UNIX-style operating system. UNIX was designed by people rebelling against nonsense like ACLs, file attributes, etc.; it was a deliberate choice.
      >>>>>>>
      ACLs and file attributes are just different implementations of metadata and security. I bet you think that utime and the rwx bits are nonsense too? As for being a real UNIX, ACL's are supported in most commercial UNIXes and file attributes come directly out of IRIX.

      XML files are supposed to identify what the XML represents. Dumping bits of XML into a file and determining its type through file attributes is contrary to everything XML stands for. Other text files encode their type as part of their file name (usually, an extension).
      >>>
      Extensions are an anarchronism. Just because they're popular doesn't mean they don't suck.

      --
      A deep unwavering belief is a sure sign you're missing something...
    4. Re:threading and typing in Linux by g4dget · · Score: 2
      You didn't even understand the implementation.

      Well, I took you at your word. Maybe you should have described it better.

      As for being a real UNIX, ACL's are supported in most commercial UNIXes and file attributes come directly out of IRIX.

      I have no idea what "real UNIX" is. All I'm saying that the original designers of UNIX didn't act out of ignorance; they excluded ACLs and attributes from the design by choice. I think that choice is still the right one.

      Extensions are an anarchronism. Just because they're popular doesn't mean they don't suck.

      Actually, it seems to me that BeOS is the anachronism, because it doesn't exist anymore. Certainly, reviving decades old ideas like attributes and ACLs didn't make BeOS modern.

      What I can't figure out about Be zealots like you is--why don't you just use Windows? Windows has all the features you pretend to like so much: it has a fully attributed file system, it supports ACLs, and it has a library-based graphics API, just like BeOS.

    5. Re:threading and typing in Linux by Howie · · Score: 1

      "and it has a library-based graphics API, just like BeOS. "

      actually Windows has several library-based graphics APIs, which are apparently released or updated or superceded roughly every three months. Or so it seems from trying to keep up with what MS consider current in the world of Multimedia or Game application development.

      "why don't you just use Windows?" - I'm wouldn't consider myself a BeOS zealot (I am/was a registered developer, but I haven't run the OS in at least a year), but why should they? The same argument applies to Linux or *BSD for most people - good hardware support etc... why don't we all just stop burying our heads and use Windows?

      --
      "don't fall into the fallacy of believing that Perl can solve social problems. Maybe Perl 6 can, but that's a ways off"
    6. Re:threading and typing in Linux by Anonymous Coward · · Score: 0

      a library-based graphics API, just like BeOS

      WOW! A library?!? For a GUI?!? My God, BeOS certainly took computing into the next decade. You say that Windows has libraries? Say, are you sure about this? Its a pretty radical idea you know, using a library to interface to a GUI!

      Qt, GTK+, Motif, Xt...man, those libraries don't do graphics! Oh, shit, wait...

      YUO = CLUELESS MORON

    7. Re:threading and typing in Linux by smallpaul · · Score: 2

      Most files have no detectable fingerprint and this will only become more common as more text-based formats (XML) proliferate.

      What better fingerprint do you want than an XML namespace?

  77. dead like dirt by Anonymous Coward · · Score: 0

    Of course it's dead. You can't even find a SSH2 client for it, let alone software that meets your needs.

    It was a good try, and BeOS had a great idea, but it's time to let it go.

    1. Re:dead like dirt by prepp · · Score: 2, Informative

      hmm thats strange im using sshd and ssh from the 2xx branch.. oh well its my imagination then...

      granted the sshd build is a bit flawed but not unsecure.

      http://www.bebits.com/app/2894
      http://www.bebit s.com/app/2741

      --
      "There is hopeful symbolism in the fact that flags do NOT wave in a Vacuum " --Arthur C Clarke
  78. Re: English 101 by Anonymous Coward · · Score: 0

    Damn, I was thinking that you might know what
    the hell you were talking about and then you
    did that idiotic lose / loose transposition and
    I knew it was all wrong. Better luck next time.

  79. from Joe User by Anonymous Coward · · Score: 1, Interesting

    Me, I'm Joe User. I run WindowsXP cau that's what everyone else uses. I got Windows in 98 to tag along the internet thing, and it's great.

    I'll tell you what tho - Windows is unsatisfying as an OS. I've never compiled a linux kernal, don't know crap about what distinguishes Unix from Linux, and the only programming I know is BASIC from back when I was a teenager using a black and green AppleIIc.

    What I read here about BeOS isn't an OS that's all-geeck no-chic; I read about something that appeals to me, an average user, who niether knows nothing about putting up a server nor needs to have telnet or ftp or a bunch of other crap in an OS. I don't wanna recompile my kernal, or design my own drivers like I hear Linux folk do. I want my computer to boot up like my television, to do what I tell it, and to not crash on me.

    Since my computer serves as my multimedia playcenter, sending music and video to my home theater blah blah etc, here I am reading about an OS that has everything I could want: a multimedia based OS that's stable, intuitive, user friendly, and stable.

    People can claim all they want about XPs enhanced functionality (and yes it does play games well) or Linux'es stability, but for me, Joe User, that's a bunch of crap I don't need.

    AFAIC I'm gonna give BeOS a try on my 2100amd equipped system for kicks. If that doesn't work I consider myself lucky to have an older 500mhz with a 3dfx in the closet that I can try it out on. For all I know, this may be just what I need to get over the sluggishness and bloat that is XP. A nice petite OS with blazingly fast speed and great multimedia support sounds like exactly what I've been looking for.

    1. Re:from Joe User by mmu_man · · Score: 1

      If it doesn't work on AMD Athlons XP or old P4, that's because they are buggy, not BeOS. :^]
      (and you know what there is even a patch :)

  80. Re:OSes Never Die by Anonymous Coward · · Score: 0

    > vertical markets

    Fuck off, troll.

  81. Get a clue by dh003i · · Score: 2

    Get a clue, man, licensing something under a Free Software license like the GPL does not mean giving it away for free.

    Nothing in the GPL forces you to offer your binaries, source-code, or ISO's available for free download from the net. It only requires that you (at least) allow those who want the source to get it at the physical price of delivering it.

    You can, for example, sell a CD with only the binaries and an installer on it, along with an offering to deliver the source code at the cost of shipment. Alternatively, you can include the source on the CD you sell.

    The important point from a business point of view is that you neither have to offer the source nor the binaries on the web for download; though, in most cases, offering the source for download will not hurt business (though offering the binaries for download probably will).

    Most people who are your target customers do not want to compile something from scratch. They probably don't even know how to do it. So offering the source for distribution under the GPL has little if any effect on your business.

    So in short, the point is that if you do things right, you can have a viable business model based around GPL'ed software. For the most part, this means NOT offering the binaries for download for free on the web. As for the source, that's largely a non-factor from a business standpoint; though it may be best to offer it for download on the web for public relations.

    OSI-compliant and FSF-compliant software may not be an all-encompassing savior for businesses. But if implemented right, it can hardly hurt.

    And once again, neither Open Sourced Software nor Free Software means you necessarily get something for free. Most things which are Open Sourced Software or Free Software *happen* to be free as in they can be downloaded for free; that does not mean that OSS or FS software *must* be free as in downloadable for free.

  82. Re:OpenBeOS: not here now, alternatives available. by NDPTAL85 · · Score: 1

    By the time OpenBEOS is ready both Windows and Linux will be everything everyone could ever possibly want or need them to be. You're just fighting too big of a grain man. Give it up.

    --
    Mac OS X and Windows XP working side by side to fight back the night.
  83. Re:Oh yeah? I can list plenty of dead OS's... by strat · · Score: 1

    RT-11 and RSX11M are in my basement, if you must know. As soon as I can get media that doesn't require 3-phase, TOPS-20 will be as well.

  84. Not terribly accurate, wishful thinking by Alderete · · Score: 2, Insightful

    This article contains a number of inaccuracies and omissions, which leads one to wonder if the author is not writing with rose-colored glasses firmly in place:

    1. "BeOS is fully POSIX compliant" -- not correct; it would be more accurate to say "mostly" rather than fully. I could quote from the Be FAQs on this point, because I wrote the original FAQ (I worked at Be for three years).

    2. USB & FireWire support -- the article states that the USB support is not very complete, and shortly thereafter implies that FireWire is supported more fully. It's really more the reverse, though I doubt if the USB code would work with much of the built-in USB hardware being released these days (you never know, though; we got the original stack from Intel). At any rate, if you happen to have a BeOS retail box, you'll see USB listed (along with the Intel credit), and no FireWire (though my most current box is for R4.5, not R5).

    3. Design of the kernel -- I can't comment on a technical level, but my recollection of conversations with kernel engineers was more that the kernel was monolithic (and that we thought that was a good thing). The design inspiration was from the XINU operating system ("XINU" is "UNIX" backwards), I'll leave it to operating systems connoisseurs to determine whether that compares with the Hurd or L4, as the author asserts. Perhaps the author is thinking of a new kernel being written for the "not dead yet" OpenBeOS project(s).

    In all, the article reminds me altogether too much of the many articles about the Amiga OS that I read while I worked at Be. Sad, but true. I wish those projects luck -- I miss Be and BeOS -- but I consider them wishful thinking. I've moved on to Mac OS X, and don't plan to go back.

    Maybe the team now at Palm will change my mind -- I hope so!

  85. Dead or Alive? ... by turki · · Score: 1

    Well ... As long as the community is still in love with BeOS ... it's alive and no way dead! ... Long life, BeOS! ...

  86. Fuck BeOS by Anonymous Coward · · Score: 0

    I hate fucking BeOS and anyone who uses that piece of shit OS should be anally raped by having their out of date shit ass machines shoved up their asses.

    1. Re:Fuck BeOS by stevejsmith · · Score: 1

      I sense much hatred in you my child... Argh, I have to learn to type slower, this 20 second rule is getting annoying!

  87. lets be honest by Anonymous Coward · · Score: 1, Insightful

    Ok...

    I tried BeOS as my primary operating system for 3 months (this was a prior release over the final). I returned once again during the final release for a very short period. My roommate was a huge fan of BeOS and he stuck with it til the end. (At which point we thoroughly converted him into a Linux lifer).

    While I truely enjoyed all the very technically pleasing asepcts of the operating system... there were problems. I really did admire the file system, threading, memory management and unix style xterm/console... there were problems.

    Driver support was absolutely appauling. I know, I know, it did not have an amazingly huge installed user base and these things naturally follow. However, if we are going to stand idly by and watch BeOS be touted as the world's greatest creation, lets just be honest.

    Application support was non-existant. There were no decent browsers and a hand full of applications that implemented only the very basic's. I have horrible memories about non-intuitive UI implementation in the provided applications and utitilities.

    They really did a great job of implementing the fundamental foundation. However, a great home has more then just a nice starting base.

    Its great it recovered from application crashes and would know when to auto-magically kill problems. In fact, with the frequency in which applications died it was quite necessary. At the time, it was admitted that tracker was horrible, but was just until something better was going to be released. I had more the one instance where networking would bomb out and never ever return to a functional state. This was truely fixed in 4.5? I really could go on for quite a while. I wanted to fall in love with this operating system, but its less important features that actually effected the user in some noticleable way just never got addressed.

    I'm not sure what the author is smoking, but I could take a guess its the same thing Balmer hits before he goes out to praise MS.

    Yes, I'm posting anonymously too. I'm not lavishing any portion of this, these were all my experiences under the very technically elite skeleton BeOS was.

    1. Re:lets be honest by prepp · · Score: 1

      i do consider it really is that funky sheit that arnold smokes in his movies ;D

      --
      "There is hopeful symbolism in the fact that flags do NOT wave in a Vacuum " --Arthur C Clarke
  88. Maybe you didn't understand. by Inoshiro · · Score: 2

    IBM gave Netscape Communications (back before they were bought by AOL) lots and lots of money. They setup agreements specifically so that Netscape 2's codebase with extensions to Javascript and plugins would be released for OS/2 in 1997. It was fairly comparable to Netscape 3.0 on Windows at the time. BeOS never got a browser that was any good until Opera put out a port. It never really became a popular one.

    As for the moderation, I'm sure meta-moderation will clear that up. Net+ sucked ass. The community, not the company, were the ones who managed to get a browser for their OS that wasn't crappy.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  89. Dano - BeOS Pro 5.5/6.0 by Anonymous Coward · · Score: 0

    It's out there. I'm doubtful the source is floating around, but there are cobbled together builds from developer releases with the new BONE networking and OpenGL, along with numerous bug fixes. As long as people are writing drivers, and the cool-ass BeOS replacement projects continue, BeOS lives.

    Music For Trolls
    http://www.mp3.com/highc

    1. Re:Dano - BeOS Pro 5.5/6.0 by Anonymous Coward · · Score: 0

      *cough* http://snotling.free.fr *cough*

  90. BeOS download archives still get many visits by benners · · Score: 2, Informative
    Hi,
    BeOS is NOT dead!
    I am running a non-commercial download archive for BeOS with more than 1.300 entries,
    over 2.300 visitors a day and more than 300 gigabytes of traffic a month.
    - This is too much for a dead os! ;-)

    http://bezip.de

    Ciao,

    Sebastian

  91. Be mistakes by master_p · · Score: 1

    BeOS was an excellent operating system in many areas. But Be did some mistakes:

    1) they did not allocate enough programmers for writing device drivers

    2) they did not make an Office suite

    3) they abandonded the BeBox

    Building a cool OS is not enough. After version 4.5, they should have allocated some more resources building device drivers and an office suite.

    There also was a major drawback in the BMessage class: if the app did not process messages fast enough, it ended up loosing messages.

    They could have made it if they followed the Apple model.

  92. Re:Oh yeah? I can list plenty of dead OS's... by sql*kitten · · Score: 2

    So where is RT-11? RSX? Venix? PRIMEOS? CYBER NOS/VE? HP MVS? Lots of operating environments have come and gone...

    I work in the finance industry and I can practically guarantee that within 20 mins walk of my office you will find all of those operating systems still in production use. The combination of extreme urgency and extreme aversion to risk in this business means that there are some very strange configurations in use today that doubtless made perfect sense at the time and far outlive their original designer's intentions.

  93. Best OS Ever by Anonymous Coward · · Score: 0

    BeOS is still the most elegant and friendly OS I have ever used. The only thing close speed wise is QNX Neutrino. Ah Be, I was pulling so hard for you. You had it all, and even you could not survive. I still think you should have sold out to Apple when you had the chance.

  94. Re:Dead? For 50 years? by vortexau · · Score: 1

    A customer enters a Bomber shop.

    Customer: 'Ello, I wish to register a complaint.
    (The owner does not respond.)
    C: 'Ello, Miss?
    Owner: What do you mean "miss"?
    C: I'm sorry, I have a cold. I wish to make a complaint!
    O: We're closin' for lunch.
    C: Never mind that, my lad. I wish to complain about this Bomber what I
    purchased not half an hour ago from this very boutique.
    O: Oh yes, the, uh, the Boeing Blue B-52 ...What's,uh...What's wrong with it?
    C: I'll tell you what's wrong with it, my lad. 'E's dead, that's what's
    wrong with it!
    O: No, no, 'e's uh,...he's resting.
    C: Look, matey, I know a dead Bomber when I see one, and I'm looking
    at one right now.
    O: No no he's not dead, he's, he's restin'! Remarkable Bomber, the Boeing Blue B-52, idn'it, ay? Beautiful fuselage!
    C: The fuselage don't enter into it. It's stone dead.
    O: Nononono, no, no! 'E's resting!
    C: All right then, if he's restin', I'll wake him up!
    (shouting into the hangar)
    'Ello, Mister bomber B-52! I've got a lovely fresh bomb load for you if
    you show...(owner hits the hangar)
    O: There, he moved!
    [This message was re-edited by voretxau on January 29, 2002 at 20:02.]

    --
    (David Bowman, EVA near HUGE Monolithic Win-PC in orbit around Jupiter) "My God - its full of Malware!"
  95. Re:Oh yeah? I can list plenty of dead OS's... by King_TJ · · Score: 2

    Excellent post!

    I completely agree. I had a number of discussions about BeOS and its merits with one of my friends who does software development for a living. He was a huge BeOS fan, and is probably the one responsible for me giving it a good second look. (I installed a free copy I received with a magazine, but quickly uninstalled it after it didn't seem very useful at first glance.)

    It seems to me that most BeOS fans are, in fact, software developers. Most of the really powerful features inside BeOS are only appreciated by a developer. (Users really don't care how threads or objects are handled, as long as they like the look and feel, and functionality of whatever software they're using!)

    I think this is what will lead to its eventual death, and certainly what caused the end of its original production and updates.

    First and foremost, an OS has to cater to its *users*. For an operating system that was so "developer friendly", I didn't see all that much real development going on. You had the typical re-hashes/ports from the Unix/Linux world, and a relative "handfull" of original programs. Much of the shareware I downloaded for BeOS was quite bug-ridden and broken. Sure, they did regular updates - but you shouldn't have to suffer through 4 or 5 updates to your favorite IRC client before you get one that quits crashing and shutting down during use.

    Not only that, but if there was any supposed "niche" potential to BeOS, it was supposed to be multimedia. Where was the firewire support for downloading from DV camcorders, then? Where were the up-to-date video drivers for high-performance cards? Where were all the hard disk recording and MIDI sequencers? (Sure, someone had 1 or 2 shareware MIDI sequencers for BeOS - but at least give me *one* commercial "standard" in a Be version! Cakewalk? Steinberg CuBase? Logic Audio? Nope.... not there.)

    It seems to me like this was really an OS that died before it was even ready to get started. It probably could have gone someplace if they built the apps and secured deals with commercial vendors to port to it BEFORE it was officially announced to the public.

  96. As does HP... by Anonymous Coward · · Score: 0

    Two totally different OSs, same name. MVS runs on the HP-3000 series minicomputers, pretty much the same hardware as the 9000 (PA-RISC), but with a different boot loader prom.

  97. Re:Oh yeah? I can list plenty of dead OS's... by zonker · · Score: 0

    So where is RT-11? RSX?

    right here of course :)

  98. Re:Oh yeah? I can list plenty of dead OS's... by Anonymous Coward · · Score: 0

    And I can list a few decent apps written for BeOS

    Gobe Productive
    Tune Tracker

    Nuendo was developed for BeOs but at the last minute thank's to a directionless Be Inc, it was dropped but the beta was running rings around the Windows version.

    There was also Personal Studio for Video editing which could perform transition effects on BeOS systems where Windows/Mac systems required dedicated DSP Hardware to get the same real time results.
    I'm not saying it was a Final Cut Pro killer by any means but it definately showed the potential of the OS platform.

    SoundPlay is another app that really rocked, yeah not as pretty as WinAmp or XMMS but more capable as far as audio was concerned.

    I really pine for the day when Open BeOS becomes a reality and I hope to push hard for it to become a decent Audio Creation Platform cause Windows and Mac both are bloody inept and don't even start with Linux. As a platform for audio creation it is pathetic.

    End of Rant.

    blitze

  99. Business users drive the market by Art+Tatum · · Score: 1
    The reason BeOS and AmigaOS died is because they didn't offer the business community anything. If you want to succeed in the desktop OS market, you have to give *business* users something better than what they've already got. And it would have to include looking and acting just like Windows (so they don't have to retrain anyone) and running all the old Windows (and maybe even DOS) applications as fast or faster than they run natively. More or less, Microsoft is going to continue to own the desktop market until they do something so monumentally stupid that they die in the eyes of business users.

    As a musician, I understand the glory of NeXTSTEP, BeOS, and AmigaOS; but catering to the artistic community is not going to be successful economically. The segment of the market that Microsoft doesn't have belongs to Apple; and probably always will.

    Now, since Apple bought NeXT, there's at least *some* "trickle down" of decent technology to the artistic community. But pure, fine, newly-engineered, beautiful technology will never survive as a commercial desktop OS venture. Only Free Software can afford to take the time to do this.

  100. Last Post! by alpg · · Score: 1

    Thus spake the master programmer:
    "Let the programmers be many and the managers few -- then all will
    be productive."
    -- Geoffrey James, "The Tao of Programming"

    - this post brought to you by the Automated Last Post Generator...