I just downloaded it and put it in a virtualbox vm. It's very fast and clean. I like it.
An introduction to the Haiku OS
21–30 of 71 posts
Re: An introduction to the Haiku OS
#22Earlier quoted context omitted.
Devil's advocate: If Be became OSX, we probably wouldn't have ever seen the iPod, iPhone or iPad.
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.
Re: An introduction to the Haiku OS
#23Several 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…
4. The biggest problem with BeOS back in the day was lack of applications. I don't see this being fixed with Haiku unless they have translation layer.
I don't know... it seems like most of the benefit of Haiku is in the unique APIs. What's the point of using it if you're just using apps from other platforms?
Would you have said the same thing about iOS? That iPhone should've had a translation layer so it can run Windows Mobile apps, because the app store was empty?
At some point, if you're trying to build an innovative platform, you just have to grit your teeth and do what you can to attract native apps.
Re: An introduction to the Haiku OS
#24Re: An introduction to the Haiku OS
#25I 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.
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.
Re: An introduction to the Haiku OS
#26Several 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…
4. The biggest problem with BeOS back in the day was lack of applications. I don't see this being fixed with Haiku unless they have translation layer. I don't know... it seems like most of the benefit of Haiku is in the unique APIs. What's the point of using it if you're just using apps from other platforms? Would you have said the same thing about iOS? That iPhone should've had a translation layer so it can run Wind…
Sure, I agree with that statement in principle. Though I don't see Haiku capturing a market the size of even WebOS or something like that, it just doesn't seem that there is enough space for it.
The only reason I mentioned translation layer was to get people using it...but it they plan to write some awesome apps for it, all the better.
It really is a catch-22. Look at Ubuntu and Wayland. Getting to Wayland means having to write quite a few apps that are there on X11 stack, but if you just use a pass through or translation layer, what incentive is there to write more apps? So, yeah...you are right, sometimes you just have take it for a bit with few apps if you think you have the audience. Clearly Ubuntu has the audience. Does Haiku?
Re: An introduction to the Haiku OS
#27OS X's Spotlight is a remnant of BeOS. Apple hired Dominic Giampaolo who did most of the design and implementation of BeFS early in the 2000s. Both systems use metadata stored in the file system for indexing, but BeFS was more through and had better query support. There was hope that a filesystem close to BeFS would be the default OS X FS.
Re: An introduction to the Haiku OS
#28I 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. 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.
To be clear, I was disagreeing with the article, not the rationale for Haiku's existence.
Re: An introduction to the Haiku OS
#29Earlier quoted context omitted.
4. The biggest problem with BeOS back in the day was lack of applications. I don't see this being fixed with Haiku unless they have translation layer. I don't know... it seems like most of the benefit of Haiku is in the unique APIs. What's the point of using it if you're just using apps from other platforms? Would you have said the same thing about iOS? That iPhone should've had a translation layer so it can run Wind…
Sure, I agree with that statement in principle. Though I don't see Haiku capturing a market the size of even WebOS or something like that, it just doesn't seem that there is enough space for it. The only reason I mentioned translation layer was to get people using it...but it they plan to write some awesome apps for it, all the better. It really is a catch-22. Look at Ubuntu and Wayland. Getting to Wayland means havi…
Not sure Haiku will ever be more than a hobby.
My appreciation for it is that it has been a long, long, long labor of love for its developers.
I can't help but to admire the dedication of everyone who made it happen. I don't think that widespread adoption was anything they had in mind.
Re: An introduction to the Haiku OS
#30I 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. 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.