This shouldn't be an issue, but I'm afraid it is: it still looks like a late-90s OS. That should be a top priority for the Haiku project.
Yeah, get some lens flare and transparent windows in there!
You forgot drop shadows.
An introduction to the Haiku OS
31–40 of 71 posts
Re: An introduction to the Haiku OS
#32single user only os? i'm sorry, but there's no way that it can become popular with that limitation. security is too much at risk here, didn't we just manage to convince microsoft that computers shouldn't start as root all the time? also, seeing that it's geared towards multimedia, there's no way that any real multimedia company will adopt the software with no file permissions and user access to all root powers.
The iPad seems to be doing ok with that limitation.
Re: An introduction to the Haiku OS
#33Earlier quoted context omitted.
What makes you say that? I think BeOS / OSX could've been a fantastic embedded platform to build an iOS type device around.
Tiles answered the main part of your question (Steve Jobs), but to respond to the embedded part, Palm never did anything useful that I know of with their purchase of BeOS, which is unfortunate.
By the time Palm bought Be Inc., they had all but stopped doing anything useful with anything. Other than the Treo smartphone line they bought from Handspring, they only had a few good models from 2002-2005, and since then they've only achieved notability by not going bankrupt and instead getting bought.
Re: An introduction to the Haiku OS
#34Earlier quoted context omitted.
I can't see what Haiku offers that modern OS X doesn't. That's not really the point. Haiku's intent is to keep BeOS alive. At the time (over 10 years ago), BeOS was the epitome of a modern OS. The pickings were slimmer back then. Of course, it took almost that long to make Haiku happen, and the OS world has changed significantly since then.
For a "modern OS" BeOS lacked a lot. Shoddy hardware support at best, a terrible network stack, did it have a printing subsystem? I know they wanted to rebuild the networking stack I don't remember print being good. Internationalization was non-existant. It was an RTOS with a UI on it, sexy and clean, I'm not a hater but a long long long way from NextStep or OSX.
To be fair, much of the needed work was accomplished in the Dan0 development release that was leaked near BeOS's demise. This included the BONE network stack and some 3D support. Everything about Dan0 was, of course, very much development code, but it was definitely a marked improvement over R5. Haiku was able to use some of the Dan0 high level kits in place until rewrites could be made.
Clearly the Apple/Be Inc. issues were sorted out to Apple's benefit, but it's still neat to see what could have been. OS X had its own issues in its widely released beta, after all. ;)
Re: An introduction to the Haiku OS
#35single user only os? i'm sorry, but there's no way that it can become popular with that limitation. security is too much at risk here, didn't we just manage to convince microsoft that computers shouldn't start as root all the time? also, seeing that it's geared towards multimedia, there's no way that any real multimedia company will adopt the software with no file permissions and user access to all root powers.
The iPad seems to be doing ok with that limitation.
The iPad does not have that limitation. Applications are not run as root. If they were there would be no need for jailbreaking.
Re: An introduction to the Haiku OS
#36single user only os? i'm sorry, but there's no way that it can become popular with that limitation. security is too much at risk here, didn't we just manage to convince microsoft that computers shouldn't start as root all the time? also, seeing that it's geared towards multimedia, there's no way that any real multimedia company will adopt the software with no file permissions and user access to all root powers.
This is tangential to Haiku, but maybe security shouldn't rely on the concept of users (ahem, EROS, while we're talking about obscure dead OSes).
Re: An introduction to the Haiku OS
#37Several things 1. I'm an OS junkie. I love installing, fiddling and learning new OSes. I installed BeOS and used it for about 2 years (no joke) back in the day. LOVED IT. I even had it replace my Slackware instance for about 6 months as my primary system. 2. I love seeing OSes still actively developed even if they aren't popular. I think it keeps driving ingenuity and pushes other people. But, I don't get why we have…
I remember being able to play 4 qvga sized movies simultaneously on a Pentium (the first one) running BeOS with no hiccups. Impressive in those days. Honestly, after all these years, I had major doubts that Haiku would ever be released. Glad to be wrong.
I have first gen ( dual 66 ppc ) and second gen ( dual 133 ppc ) beboxes. i ran far more than 4 movies with no hiccups. so much more. the media performance on the BeOS back in the 90s w/ a tiny amount of RAM still blows away any OS I have used.
Ever GUI OS I have used before that or since then has seemed like a bloated slow old pig in comparson.
Re: An introduction to the Haiku OS
#38I can't see what Haiku offers that modern OS X doesn't. Drag and Drop between applications? Got it. Combining soundcards to use in aggregate? Got it[1]. Object Oriented APIs? Had it since NeXTSTEP (and they're called 'Kits' as well). The only thing that seemed mildly interesting to me was the routing of audio between apps, but this is mostly achieved these days using ReWire or Soundflower (admittedly not an ideal sol…
> I can't see what Haiku offers that modern OS X doesn't.
It is free and it doesn't require proprietary hardware?
Re: An introduction to the Haiku OS
#39Several things 1. I'm an OS junkie. I love installing, fiddling and learning new OSes. I installed BeOS and used it for about 2 years (no joke) back in the day. LOVED IT. I even had it replace my Slackware instance for about 6 months as my primary system. 2. I love seeing OSes still actively developed even if they aren't popular. I think it keeps driving ingenuity and pushes other people. But, I don't get why we have…
What part of the GUI do you find clunky?
I've always like the BeOS interface... then again I also really liked CDE. There are plenty of things I would want to change about the Be interface that Haiku implements but, I think that would be iterative not replacement.
Re: An introduction to the Haiku OS
#40I can't see what Haiku offers that modern OS X doesn't. Drag and Drop between applications? Got it. Combining soundcards to use in aggregate? Got it[1]. Object Oriented APIs? Had it since NeXTSTEP (and they're called 'Kits' as well). The only thing that seemed mildly interesting to me was the routing of audio between apps, but this is mostly achieved these days using ReWire or Soundflower (admittedly not an ideal sol…
open source and not locked to the mac hardware ?