Linked by Thom Holwerda on Mon 12th Nov 2012 15:56 UTC
BeOS & Derivatives Can you believe they've come this far by now? Once known as OpenBeOS, Haiku today announced the release of the fourth alpha for Haiku R1. It seems like only yesterday when BeOS died and OpenBeOS rose form its ashes, generating a new hope among the legions of avid BeOS fans. Now, almost twelve years later, we've hit the fourth alpha.
E-mail Print r 18   · Read More · 164 Comment(s)
Thread beginning with comment 542235
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: In what sense...
by Splinter on Tue 13th Nov 2012 02:03 UTC in reply to "In what sense..."
Member since:

The full C++ API was also a dream. Well thought out and complete in a time where the Windows API was a cobbled together piece of sh*t.

Multi-threading, filesystem events etc were all there and working. There was also the mandatory call IsComputerOn so your program could know if the computer was running. Paired with IsComputerOnFire you could handle significant failure conditions right within your code. ;)

Reply Parent Score: 2

RE[2]: In what sense...
by henderson101 on Tue 13th Nov 2012 12:24 in reply to "RE: In what sense..."
henderson101 Member since:

The C++ was actually a blessing and a curse. It tied Be to a very specific compiler for a very long time. It was hard to expand the API without a lot of planning or creation of second versions of the classes (they seem to have been doing this for the BeIA project as there's a second namespace with different classes in the Dev kit I've used.) Adding methods to existing classes was costly as they reserved only a number of "slots". Using them up would cause a lot of issues.

The API being multi-threaded was cool, but it forced a lot of uncomfortable synchronisation on to the developer. There was no middle ground - you either adapted or your app sucked. It had the potential to make really simple operations very complex.

Reply Parent Score: 2