6 ms·
What was the outcome of the discussion about switching to the Linux kernel?
by wmf 12y ago
What was the outcome of the discussion about switching to the Linux kernel?
- joshuapants 12y agoDo you have a link to where this was considered? This seems like it would nuke almost the entire point of Haiku, since the goal isn't just to be a desktop environment.
- vinkelhake 12y agohttp://www.freelists.org/post/haiku-development/Whats-the-status-of-Haiku http://www.freelists.org/post/haiku-development/Whats-the-st... The discussion was quite interesting. There were basically two camps. One that wanted to focus on the "product" side of Haiku and leverage the superior hardware support in Linux. The other saw the development of the Haiku kernel as a goal unto itself.
- gillianseed 12y agoWhy would relying on an existing kernel (linux, bsd) 'nuke' the point of Haiku ? The API's (kits) would not have to change in any way, which is the part that application developers face, and from a user perspective the only difference would be better performance and much better hardware support. The 'point' of Haiku (and BeOS before it) has (in my opinion) always been to provide an OS that is designed for desktop use with the apps integrated well with the desktop environment, I don't see how that in any way excludes using existing kernels since the 'desktop part' is outside of the kernel anyway.
- joshuapants 12y agoFor one I'm pretty sure it would wreck binary compatibility with BeOS without the addition of a compatibility layer. Whether you think that's a worthwhile goal or not, it is a stated goal of the project. Linux also lacks the pervasive multithreading that BeOS and Haiku have. Again, maybe that approach isn't the best one, but it's a pretty big feature of BeOS/Haiku and switching to something else would make them more ordinary. I think they only have a chance to survive as long as they're novel.
- gillianseed 12y ago>For one I'm pretty sure it would wreck binary compatibility with BeOS without the addition of a compatibility layer. There's already 64-bit Haiku binaries which can be used alongside the old BeOS binaries so I doubt that this is an issue, it's not as if programs call the Haiku kernel directly, it's done through the Kernel kit. >Linux also lacks the pervasive multithreading that BeOS and Haiku have. Again, maybe that approach isn't the best one From what I've read from the guy who is working on improving Haiku scheduling (pawel), the thread scheduling was really bad in Haiku and scaled poorly, he was also positive (despite all his work on the Haiku scheduler) of using a Linux/BSD kernel to improve performance. It's not as if rendering a tea-pot while opening 3 videos is causing any modern kernel scheduler to choke these days, it was impressive back when people were running windows 95. In short, I don't think BeOS pervasive multithreading offers any benefits against modern kernel schedulers of today. >I think they only have a chance to survive as long as they're novel. I agree, however I don't think Haiku's novelity lies in which kernel it uses as it is such a low level part of the stack, it's in the API's, the desktop environment and the file system, in other words, user/developer facing components.
- gillianseed 12y agoIt seems it was just someone trolling, no code has surfaced at all. Still the discussion it generated was interesting.
- ashark 12y agoThat's good, since I'd assume that if it were possible to deliver as nice a desktop experience as BeOS on an OS with the Linux kernel someone would have done it by now. Then again, maybe it really has been X's fault all along. I guess we'll find out with Mir and Wayland. [edit] fix broken sentence
- dnautics 12y agoIt would have been interesting to create a version which was a Linux binary compatibility layer, essentially compiling libbe.so for Linux, with the intent of swapping it for a native kernel later. However, I think this might have been technically difficult since iirc beos uses the same interrupt for syscalls as Linux but does not use the odd Linux syscall standard (where short parameter lists are put into registers) versus the stack, like freebsd. I think freebsd might have been a better choice for that reason and also its performant kernel.
- Torgo 12y agoOne of the goals of Haiku is to be able to run BeOS software unaltered, and an unfortunate side effect of this is that the ABI for BeOS software is compatible with 1998 GCC, version 2.9 or thereabouts.
- geon 12y agoI think that is only a goal until the 1.0 is reached, in order to focus the effort.
- ab5tract 12y agoI can see the "focus the effort" part, but it has always seemed like a case of personal determination amongst core members. It's been argued that if the ABI compatibility were not considered a requisite, this effort would have shipped some really cool stuff by now. I just want to know which BeOS software these people have that they need to run. They've never made clear just which software requires this extend-efforts-by-a-decade-or-more requirement.
- vlunkr 12y agohttps://www.haiku-os.org/about/faq#top_5 https://www.haiku-os.org/about/faq#top_5 They talk about it here. They say Linux is needlessly complex for a desktop OS.