What is the point of BNX?
As stated on OSNews, Sven Jorg is slapping all of Haiku’s hard work in the way of Kits onto the QNX kernel and XFS.
I’m wondering why we need a 5th version of BeOS (R5, Bone, Zeta/Dano, Haiku, and now BNX).
But besides the eventual difficulty developing for all of them, and the user confusion that will result, what does the QNX kernel do better than the NewOS kernel that Haiku uses? I thought that the kernel was the bit that loaded all of the drivers, and that replacing the kernel would necessitate using a completely different set of drivers. I also heard that QNX had even less desktop acceptance than BeOS, and thus less drivers, so BNX would have less drivers than all of the BeOS variants.
Also, doesn’t using a completely different kernel make the idea of binary compatibility, and thus using the library of already-existing BeOS applications, impossible?
I also heard that the smooth multithreading roots of everything BeOS related would conflict with the realtime aspect of QNX.
Wikipedia mentions nothing in the way of XFS having attributes, so a huge major aspect of BeOS, which no operating system has yet to fully emulate, would be lacking.
But we have a free, opensource, fully operation kernel that goes by the name of NewOS, and this group is using a licensed, proprietary kernel that goes by the name of QNX. Why?
- BNX would use a much smaller driver base than Haiku, because of using a different kernel
- BNX would not be usable with the entire library of BeOS applications
- The QNX kernel would conflict with the multithreading roots of everything BeOS related
- XFS removes any possibility of filesystem attributes, which removes one of the biggest features of BeOS
- Haiku already has a fully operational kernel, which does not suffer from many of the deficits that Sven cites
More quirks about Sven Jorg’s interview:
He states that BeOS can not take advantage of multiple cpus, specifically by saying that Zeta must work to support “multiple cores”. If I know my history correctly, BeOS has supported “multiple cores” since 1995, according to the Be Timeline. Cores means CPUs, right?
He also states that Haiku will be exactly like BeOS, including its age, but several times, such as in app_server and the be filesystem, Haiku has fixed bugs in the original Be Inc. implementation. Also, our beloved Axel has added 64-bit cpu support, SMP, MTRR, write-combining, and >1g mem support, if I remember correctly.
So what advantages does QNX provide over what Haiku already has?