Haiku OS Resurrects BeOS as Open Source

Technical Writing Geek writes "The Haiku project, which began shortly after the death of BeOS in 2001, aims to bring together the technical advantages of BeOS and the freedom of open source. 'The project has drawn dozens of contributors who have written over seven million lines of code. Although Haiku is nearly feature-complete, there are still numerous bugs that must be fixed before it is ready for day-to-day use. The design principles behind Haiku are very closely aligned with those of BeOS. The central goal of the Haiku project is to create an operating system that is ideally suited for use on the desktop--this differs significantly from Linux and other open-source operating systems which are intended for use in a diverse range of settings including server and embedded environments.'"

Comments

Re:I suck at poetry

[doti]

by the subject of your post
i'd mod you +1 informative
indeed you suck

You are wrong

[Peaker]

You are wrong, so maybe your tone should be a little more humble :-)

Its obvious that you don't know about asynchronous I/O. Single-threaded designs are not meant for you to create threads in your event handlers, but to do your event handling asynchronously. See Twisted as an example.

This gets rid of all the thread problems, and introduces a few problems which are far easier to handle. The main problem it introduces, is that long computations or blocking operations will block the entire program. However, finding those bugs, and fixing them (e.g: converting those to be split/asynchronous, or very rarely, have their own process), is a much easier and more cost-effective process.