Linked by Andrew Hudson on Mon 20th Jun 2011 17:19 UTC
BeOS & Derivatives Haiku Alpha 3 has been in development for more than 14 months. In that time more than 800 bugs have been identified and fixed, major sections have been updated, applications have been added and updated, and great progress has been made in supporting additional hardware. Here is a summary of updates, more details can be found here. Also inside, interviews with some core Haiku developers.
Permalink for comment 477928
To read all comments associated with this story, please click here.
RE[4]: Looking Forward to Haiku
by Not2Sure on Tue 21st Jun 2011 06:36 UTC in reply to "RE[3]: Looking Forward to Haiku"
Member since:

"Lol, what seriously is a "modern" kernel. What's next a postmodern kernel?

Is that a serious question?

Yes, that's a serious question. WTF is a "modern" kernel, and WTF is a "premodern" kernel when the few decades-long history of "modern" computer science reveals a recycling of old ideas "rehashed" as innovative.

Modern, lol. Also spare me the User ad hominem. Been doing this alot longer than you, trust me. That is the whole point of microkernel (no wait, nanokernel!, no wait picokernel!) design.. simplicity and correctness at the cost of performance (to an arguable extent).

Finally, I think you overestimate kernel development effort, probably because you are doing some hobby work in that area yourself? Compare the effort involved in the Linux kernel by any "engineering" metric (man-hours, SLOC) and it pales in comparison to projects in userspace. The hard "work" in operating system delivery is HAL/drivers. Plain and simple. Some people wanna call that kernel development, but we know better.

Take a step back from what you are doing before throwing around black-box terms like "complexity" unless you are prepared to discuss what that actually means because generally speaking the cyclomatic complexity of kernel code is (and should) be signficantly lower. But there aren't even real metrics to talk compare 2 bodies of code now are there? That is how haphazard software engineering is.

Reply Parent Score: 4