4 ms·
Not really. The underpinnings of the OS were fairly basic. I was a heavy BeOS user. I owned a BeBox. I developed for the OS. There was a *lot" of stuff under t
by memsom 9y ago
Not really. The underpinnings of the OS were fairly basic.
I was a heavy BeOS user. I owned a BeBox. I developed for the OS. There was a *lot" of stuff under the hood that made the OS very immature. I just didn't sit here listing them. Highlights:
Messaging was flaky prior to R5.1. The BMessage got copied a lot, and the Ports used for messaging could get clogged and then messages got dropped. Quite fatal.
The API was multi threaded - it was a concept that at the time a lot of developers struggled with. It could be extremely complicated to port apps.
A lot of the code was rough and some of it badly documented. So, the guy who worked on it knew it worked, but I doubt many other people did outside of their team. They cut a lot of corners. For example, OpenGL was a disaster. I was told the original dev left and no one was able to support what he left. It never really got back up to the level he had it up to prior o the focus shift.
Media Kit ended up getting a rewrite.
There was quite a bit of 3rd party code in the OS. Some was licensed. Some was GPL. Some of the GPL was a little questionably used, given the license. This is quite probably one of the reasons the OS was never open sourced.
- badsectoracula 9y agoI see, thanks :-). You say that some parts (Media Kit) got rewritten, were the issues BeOS fixed later? Some (BMessage copying, multithreaded API) sound like design issues, do you think that they could affect Haiku despite being a from scratch rewrite?
- memsom 9y agoThe messaging system got a massive overhaul between R5.03 (R5 was code-named "Maui") and the leaked R5.1 (aka "Dano".) They did a lot of stuff to improve it. Dianne Hackbourne wrote a massive post about it on OS News[0] around the time the OS was leaked. [0] http://www.osnews.com/comments/7057#236889 http://www.osnews.com/comments/7057#236889