
The Haiku project has reached a very important milestone. Bruno G. Albuquerque (bga) wrote the
following note attached to a commit a few moments ago:
"vnode_path_to_vnode() now returns B_NOT_A_DIRECTORY instead of B_NOT_ALLOWED as expected by POSIX programs. This allowed me to compile Haiku under itself without any hacks at all, so I guess this means that now we are officially self-hosting!" The
official announcement can be found in the mailing list. In addition, there's a new
Haiku alpha 1 status update.
Member since:
2008-04-01
I agree we shouldn't get overexcited, but I have to disagree when you imply Haiku can't be used as a day-to-day OS.
On the contrary, I'm posting this from within Haiku on real hardware! I also have R5 on this same system, and I can honestly tell you that Haiku is much nicer to work with. My network card "just works" without configuration (not only do I have to configure it in BeOS, but network connectivity is so flaky as to be unusable). In Haiku, the native resolution on my monitor is supported, whereas in BeOS I have to endure stretch mode.
Sure, I don't have many of the applications I have in Linux or Windows, but how is that different than BeOS?
Stability is quite good IMO. Rarely does the kernel itself crash. Speed is another matter, as the system hasn't been optimized.
So I guess what I'm saying is: Should we give the impression to new users that they can replace their installation of Windows, Linux, or Mac with Haiku and be okay? Of course not. But the OS *is* useable day-to-day, and it is quite stable given that it's pre-alpha quality. There's still plenty of work to be done, to be sure, but I believe Haiku's quality has already surpassed that of R5. (YMMV, of course, and I acknowledge that.)