Live data from Hacker News

Haiku Project

haiku-os.org

11–20 of 146 posts

Re: Haiku Project

#11
post #7

lets hope it is not a trademark violation https://www.haikulearning.com/ EDIT: I jumped the gun on this one. Should have done a bit googling first.

Haiku OS has been around for a lot longer (2001) than Haiku Learning which was trademarked in 2013[1]

[1] http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4802:zrn...

Re: Haiku Project

#12

BeOS (the OS Haiku is a reimplemntation of) has an interesting history. It was an OS that has a fully async C++ API (very novel for it's time and even now). The fact that it was async made the OS much more responsive and had a better CPU utilization. BeOS was another company that Apple considered to purchase but they ended up buying NeXT instead. IIRC they ended up going with NeXT because BeOS didn't have networking…

Plus, the owner of BeOS wanted more than the 125$ million that Apple was willing to pay for it. BeOS was eventually sold to Palm for a "tiny" 11$ million.

Re: Haiku Project

#13
post #7

lets hope it is not a trademark violation https://www.haikulearning.com/ EDIT: I jumped the gun on this one. Should have done a bit googling first.

Do these people have a registered trademark for haiku prior to 2004 in the same territory and classification? If so, yes. If not, no. (There are grey areas, but this is all it should come down to in theory).

Re: Haiku Project

#14

BeOS (the OS Haiku is a reimplemntation of) has an interesting history. It was an OS that has a fully async C++ API (very novel for it's time and even now). The fact that it was async made the OS much more responsive and had a better CPU utilization. BeOS was another company that Apple considered to purchase but they ended up buying NeXT instead. IIRC they ended up going with NeXT because BeOS didn't have networking…

IIRC, BeOS had networking but no multi-user or printer support. The latter was pretty important for Apple's pro market at the time, which was mostly desktop publishing.

Just the other day I found a BeOS Revision 3 manual in a closet. It was the first version that Be released on x86 after getting snubbed by Apple.

Re: Haiku Project

#15
post #8

I always smile wistfully whenever Haiku/BeOS comes up... its performance and just sheer fun remains unmatched by Windows, OS X, Linux, etc (try it out in a VM). dr_dank summed it up best back in 2003 [0]: BeOS was demonstrated to me during my senior year of college. The guy giving the talk played upwards of two dozen mp3s, a dozen or so movie trailers, the GL teapot thing, etc. simultanously. None of the apps skipped…

Well let's don't get all romantic about something that was, in the end, half-baked. BeOS debuted at the dawn of the web, and it had a barely-working, userspace network stack and a web browser that essentially didn't work at all.

It had some novel APIs, a nifty filesystem, and made for a damn good demo, but there wasn't much more to it.

Re: Haiku Project

#16
post #8

I always smile wistfully whenever Haiku/BeOS comes up... its performance and just sheer fun remains unmatched by Windows, OS X, Linux, etc (try it out in a VM). dr_dank summed it up best back in 2003 [0]: BeOS was demonstrated to me during my senior year of college. The guy giving the talk played upwards of two dozen mp3s, a dozen or so movie trailers, the GL teapot thing, etc. simultanously. None of the apps skipped…

BeOS was awesome Cubase and Nuendo (Digital Work Station) but never did. I had everything all set for my studio to run BeOS and then sadly it got cancelled.

Then I was excited when Palm(Pilot) bought them and was going to bring them back. So sad it just didn't become the OS X that it was headed for.. I actually might have joined the evil Apple empire for that. (Well probably not but at least a hackintosh).

As an old timer BeOS was so far ahead of the competition it was like AmegaOS ahead of Windows and MacOS when it was released.

Re: Haiku Project

#17
post #14

BeOS (the OS Haiku is a reimplemntation of) has an interesting history. It was an OS that has a fully async C++ API (very novel for it's time and even now). The fact that it was async made the OS much more responsive and had a better CPU utilization. BeOS was another company that Apple considered to purchase but they ended up buying NeXT instead. IIRC they ended up going with NeXT because BeOS didn't have networking…

IIRC, BeOS had networking but no multi-user or printer support. The latter was pretty important for Apple's pro market at the time, which was mostly desktop publishing. Just the other day I found a BeOS Revision 3 manual in a closet. It was the first version that Be released on x86 after getting snubbed by Apple.

Ah, you are right. Networking didn't sound right.

Re: Haiku Project

#18
post #8

I always smile wistfully whenever Haiku/BeOS comes up... its performance and just sheer fun remains unmatched by Windows, OS X, Linux, etc (try it out in a VM). dr_dank summed it up best back in 2003 [0]: BeOS was demonstrated to me during my senior year of college. The guy giving the talk played upwards of two dozen mp3s, a dozen or so movie trailers, the GL teapot thing, etc. simultanously. None of the apps skipped…

Well let's don't get all romantic about something that was, in the end, half-baked. BeOS debuted at the dawn of the web, and it had a barely-working, userspace network stack and a web browser that essentially didn't work at all. It had some novel APIs, a nifty filesystem, and made for a damn good demo, but there wasn't much more to it.

The filesystem metadata queries were real-time back when spinning disks were much slower and neither the processing power or ram was comparable to what we have today. With today's machines we do not have the same experience under Windows, macos, GNOME, KDE. Feature-wise yes, performance no. Is there a technical reason we couldn't have the same filesystem integration? No, there isn't, it's just incompatible priorities and half-baked 2nd system syndrome in effect and repeated all the time.

Re: Haiku Project

#19
I love this and would use it if I could actually install it on a modern machine, say a netbook/chromebook/winbook (I'd have to hunt around for a good browser build, SSH and remote desktop, but I like to think those exist/are feasible to self-build).

Re: Haiku Project

#20

BeOS (the OS Haiku is a reimplemntation of) has an interesting history. It was an OS that has a fully async C++ API (very novel for it's time and even now). The fact that it was async made the OS much more responsive and had a better CPU utilization. BeOS was another company that Apple considered to purchase but they ended up buying NeXT instead. IIRC they ended up going with NeXT because BeOS didn't have networking…

Also: Steve Jobs founded NeXT (which didn't hurt the prospect of a sale IMHO)
Post reply on HN