Slashdot Mirror


Haiku OS Resurrects BeOS as Open Source

Technical Writing Geek writes "The Haiku project, which began shortly after the death of BeOS in 2001, aims to bring together the technical advantages of BeOS and the freedom of open source. 'The project has drawn dozens of contributors who have written over seven million lines of code. Although Haiku is nearly feature-complete, there are still numerous bugs that must be fixed before it is ready for day-to-day use. The design principles behind Haiku are very closely aligned with those of BeOS. The central goal of the Haiku project is to create an operating system that is ideally suited for use on the desktop--this differs significantly from Linux and other open-source operating systems which are intended for use in a diverse range of settings including server and embedded environments.'"

7 of 269 comments (clear)

  1. Interesting.... by fyngyrz · · Score: 5, Interesting

    But I don't look forward to the long climb up the curve of identifying and cleaning up what, going by past experience, is likely to be quite a nest of security issues.

    Having said that, if it is actually like BeOS in that it handles multimedia similarly (that is, *really* well and without even a nod towards DRM), I'd be very likely to put some effort into using it. Linux's swap paradigm is completely unsuited to applications that need to respond *right now*, OS X is just about the same (it's only been a matter of hours since I shook my fist at Leopard for swapping out things I was using), and Windows... ugh. Going completely the wrong way.

    I suppose it'll be a while yet, though. [prepares to wait]

    --
    I've fallen off your lawn, and I can't get up.
    1. Re:Interesting.... by Lally+Singh · · Score: 4, Interesting
      It sounds like what you want is a combination of:
      1. Real-time scheduling. Preferably hard-real time (for stable video)
      2. Page locking. Don't let RT tasks page out
      3. Drivers written to obey the scheduling demands (e.g. don't wait for a disk while we have an RT task ready)


      It can all be done on regular desktop OSs.

      Challenges are:
      1. Requiring RT scheduling and page locking usually require a good level of access. For that, you'll probably want a capabilities-based permission model to to keep quicktime from giving people backdoors into root access
      2. Keeping device drivers off the RT thread path. I'd honestly prefer a separate I/O processor to do that stuff, so the CPU can keep chunking along. Dedicating RT threads to one core and device drivers to another isn't a bad way to splice up modern dual-core CPUs.
      3. It's easy to end up page-locking a lot of pages in for processes, large platform shared libs & all


      --
      Care about electronic freedom? Consider donating to the EFF!
  2. Re:Evolution by Fred_A · · Score: 4, Interesting

    It would be nice to see it not only bringing back the technical advancements that once were available but to also see it bringing some new features. Applications would be nice too.

    It's nice to have all those systems, but when people are looking at creatingsoftware for an open system for the desktop, they target Linux, possibly with a side of BSD. If the result compiles on Be, that's an unintended bonus, but nobody in his right mind is going to go out of his way to make it so.

    The people of Bibble Labs who make commercial (and closed source) photography software which I buy from them sell their stuff for Windows, Mac OS and Linux (which is why I use it).

    The last time I looked at Be, it wasn't too hard to *port* Unix/Linux software to it. However it really needs to be able to "just" run it, at least for the Linux binaries (like the *BSD do with the Linux libs). Otherwise it's going to be a repeat of 1999 (or whenever that was) when everybody played with the Be live CD or created a little partition to poke at for a while, and then went back to Linux or Windows or whatever the system where his software and data lived was.

    Be was/is a nice system, among other things I liked the ideas in the filesystem. But unless there's actually a reason to use it (and there's none), nobody will. Unless you're into that kind of thing and you still have a little space next to your OS/2 partition. But then you're probably too far gone anyway.
    --

    May contain traces of nut.
    Made from the freshest electrons.
  3. Haiku is COOL! Normal desktop footprint is 60 Meg by StCredZero · · Score: 5, Interesting

    Haiku is an example of code reuse par-excellence! You can get a normal desktop footprint into something like 60 megabytes. (Not one of these cut-down small footprint distros.) It's how an object-oriented multimedia operating system should be done.

    http://video.google.com/videoplay?docid=236331448076587879

    Haiku is damn cool
    The One OS that follows
    Don't Repeat Yourself

  4. Re:What was the point of BeOS/Haiku? by Anonymous Coward · · Score: 5, Interesting

    >>Multimedia works just great on my Windows XP machine.

    Please don't take this as an insult, but the reason you feel that multimedia works "just great" on your XP box is probably because you've not seen anything better. In the same way propeller-driven aircraft were just fine until jet engines came along. BeOS *was* better than anything else at the time (Can't speak to Haiku, as I've not run it). I ran BeOS as my primary OS for several years and in those days Windows would struggle to play two (or sometimes just one) video smoothly, with well-tracked audio. BeOS had no problem on the same hardware with a half-dozen simultaneous videos. It could simultaneously import video, mix audio tracks and play video streams, render 3D graphics, etc. and when it did slow down, it did so gracefully and never failed to respond the way that Windows would (e.g. click a menu, wait 20 seconds for Win to load the code and draw the menu).

    The main thing is, BeOS was amazingly fast and responsive in the days of I486 CPUs and 128Meg RAM. Menus and UI elements responded instantly. Cold boot to completely loaded desktop, on the net, HDD light off and ready to work? Something like 15 seconds. Windows took something like 2 1/2 minutes by comparison and the HDD never quit rattling. Why? Clean design internally and small size -- about 50MB for the whole OS including sample applications, code, and demos. (Or to put it another way, about the size of one of the hundred-or-so security patches for Windows XP.)

    From a programmer's perspective, BeOS was the best-designed OS I've ever coded for. Everything was logically named, well structured and designed with threading in mind. (In fact, every window ran in its own thread). Written entirely in C++, it was just brilliantly designed and easy to code for!

    Personally, I'm pretty excited about Haiku. IMO, BeOS was the best OS from the 90s. (BeOS was created by a spin-off group from Apple France, the same group that defied Steve Jobs' direct orders and developed the Color Macintosh (early 1990s?) and saved Apple. I was profoundly disappointed that Apple chose NeXTStep over BeOS for what was to become MacOSX.

    So, that's my long-winded way of saying "give it a try! You have no idea what you're missing."

  5. Re:The design principles behind Haiku are... by samkass · · Score: 4, Interesting

    As a former BeOS fan, I agree it was a great OS, but let's not whitewash the past. They had some significant design challenges ahead of them if they wanted to go mainstream. Everything from the "fragile base-class problem", which they never really solved, to support for lots of functionality most users consider basic these days had the potential to eat away at the performance.

    BeOS had a local file search in 1997 that would rival OS X 10.4 ...which is why Apple hired the guy to help develop MacOS X 10.5.

    they were a decade ahead of their time, and got killed by MSFT because of it.

    "got killed"? Apple didn't buy them, and Microsoft encouraged VARs to not sell it pre-installed, but the simple fact is that it wasn't really valuable enough for most people to want to buy it. Windows 95, Windows 2000, linux and MacOS 9 were "good enough" for most folks across most market segments.

    --
    E pluribus unum
  6. RIP by DNS-and-BIND · · Score: 4, Interesting
    "I once preached peaceful coexistence with Windows. You may laugh at my expense - I deserve it."

    -- Jean-Louis Gassée, CEO Be, Inc.

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!