4 ms·

It seems that this project is a free and open-source inspiration of the BeOS rather than aiming to be a complete reimplementation of it. Just like what Linux wa

It seems that this project is a free and open-source inspiration of the BeOS rather than aiming to be a complete reimplementation of it. Just like what Linux was to UN*X and ReactOS was to Windows. But, judging from its recent progress: package management repos, 64 bit support and the recent software ports at ‘HaikuPorts[0]’, it seems to be already more advanced than BeOS was and already has a lot more software since its last official alpha release (5 years ago.) But yeah a pretty interesting OS, but I’d wait for it’s so called ’beta’ when ever it arrives. I’d like to try this on a Raspberry Pi or another ARM board soon. If only it attracted more developers though. PS. (Its actually 'Haiku' not 'Haiku OS' ;) ) [0] https://github.com/haikuports https://github.com/haikuports

waddlesplash 9y ago
(I'm one of the developers of Haiku -- I manage the website and am one of the leads at HaikuPorts in addition to committing to the main source tree.) The ARM port is stalled due to a lack of developer time, and has been for over a year now... The kernel is mostly ported and initializes the framebuffer but then stalls when it gets to HID and storage initialization because the USB stack isn't ported yet (iirc). Patches wanted... but we won't have much time to spend on it ourselves anytime soon. Yes, the beta release should be coming "real soon now". We're down to 2 blockers, both of which should not be that complicated to fix. And yes, it is indeed "Haiku" not "Haiku OS". :)
- monocasa 9y ago
  Is there any documentation on what the current status of the ARM port is?
  - waddlesplash 9y ago
    I know there is https://github.com/haiku/haiku/tree/master/docs/develop/ports/arm https://github.com/haiku/haiku/tree/master/docs/develop/port... but I think it's out of date at this point. Check the commit logs for the "arm" directories in the kernel, and then ask the developers responsible for that on IRC (Freenode#haiku). I don't know much about the ARM port in specific, but I'm very familiar with our build system and development model in general, so if you have questions about that I can help there.
yjftsjthsd-h 9y ago
I think it started out as trying to perfectly clone BeOS, but then in the ensuing years that became less of a priority and they started improving things in ways that could even go so far as to break compatibility.
- MrMorden 9y ago
  Breaking compatibility is mandatory; otherwise Haiku would be stuck with its C++98 API. Trying to interface otherwise-modern code with the vintage BeOS API is doable but does not exactly lead to rising property values in Tokyo.
  - waddlesplash 9y ago
    Well, we are still stuck with a C++98 API... some parts of the x86_64 core code in the kernel, since that's only ever compiled with GCC5+ use C++11, but by and large we're still C++98. (The Be API used almost none of the STL, so it doesn't really make a massive amount of difference to us. <functional> would be of use in event handling code, as well as a few other new language keywords and the like, but by and large we'd be unaffected.)
nickbauman 9y ago
I tried running the nightly on virtualbox, got through the partitioning and then it just froze...
- nickbauman 9y ago
  FWIW the following nightly worked.

waddlesplash 9y ago

(I'm one of the developers of Haiku -- I manage the website and am one of the leads at HaikuPorts in addition to committing to the main source tree.) The ARM port is stalled due to a lack of developer time, and has been for over a year now... The kernel is mostly ported and initializes the framebuffer but then stalls when it gets to HID and storage initialization because the USB stack isn't ported yet (iirc). Patches wanted... but we won't have much time to spend on it ourselves anytime soon. Yes, the beta release should be coming "real soon now". We're down to 2 blockers, both of which should not be that complicated to fix. And yes, it is indeed "Haiku" not "Haiku OS". :)

monocasa 9y ago
Is there any documentation on what the current status of the ARM port is?
- waddlesplash 9y ago
  I know there is https://github.com/haiku/haiku/tree/master/docs/develop/ports/arm https://github.com/haiku/haiku/tree/master/docs/develop/port... but I think it's out of date at this point. Check the commit logs for the "arm" directories in the kernel, and then ask the developers responsible for that on IRC (Freenode#haiku). I don't know much about the ARM port in specific, but I'm very familiar with our build system and development model in general, so if you have questions about that I can help there.

yjftsjthsd-h 9y ago

I think it started out as trying to perfectly clone BeOS, but then in the ensuing years that became less of a priority and they started improving things in ways that could even go so far as to break compatibility.

MrMorden 9y ago
Breaking compatibility is mandatory; otherwise Haiku would be stuck with its C++98 API. Trying to interface otherwise-modern code with the vintage BeOS API is doable but does not exactly lead to rising property values in Tokyo.
- waddlesplash 9y ago
  Well, we are still stuck with a C++98 API... some parts of the x86_64 core code in the kernel, since that's only ever compiled with GCC5+ use C++11, but by and large we're still C++98. (The Be API used almost none of the STL, so it doesn't really make a massive amount of difference to us. <functional> would be of use in event handling code, as well as a few other new language keywords and the like, but by and large we'd be unaffected.)

nickbauman 9y ago

I tried running the nightly on virtualbox, got through the partitioning and then it just froze...

nickbauman 9y ago
FWIW the following nightly worked.