Linked by Eugenia Loli on Mon 27th Aug 2001 05:22 UTC
Syllable, AtheOS AtheOS is a modern, free (GPLed) Operating System written from scratch in C++. A big chunk of the OS is POSIX compliant, supports multiprocessing and it is GUI-oriented (fully OOP). Today we are hosting an interesting interview with the AtheOS creator, Kurt Skauen. Kurt is talking about his views on binary compatibility in future versions, multithreading and the future of his OS in general.
Permalink for comment
To read all comments associated with this story, please click here.
Re: multithreading
by cedricd on Fri 31st Aug 2001 09:12 UTC

First about the meta-discussion here: I haven't seen any AtheOS message that would have been flooded/hidden under an hysteria of BeOS-related messages yet. At all. All I see is a board that is animated only by BeOS folks and where the (supposedly) AtheOS folks do not contribute technical stuff but only meta-discussion. And as plenty of people said, this is relevant to AtheOS as well, given how similar (cough cough) their APIs are. JBQ, I don't have the "silver bullet" argument about how though PostMessage returning a status_t is something that annoys me, it's not something I perceive as inherently bad about the OS; but maybe I can try a comparison here: The new operator. Do you always #include new.h, turn off the exception throwing, and multiply your code size by two by adding tons of success-checking lines?? I know I'll probably never do that. I wouldn't know what to put in the if(!ptr) block, simply because i don't want that to happen, period. If that happens I prefer to SEGV or whatever and have my app exterminated. Same goes for PostMessage: _theoritically_ it can fail just like new can fail, and even in real life is using some special code around write_port, as you explained, but my apps don't exhibit this behaviour and I don't want them to. As to pervasive ("perverse"? Lol. tats a good one) multithreading, I fear I'm hell bent on the same side as Sander here and cannot agree to disagree with you ;) To drive the point home, it seems to me the reason why win32 apps suck ass reg. responsiveness even though Window sNT _does_ implement multhreading well is that MS _never forced MT on developers_. So if BeOS was the same people would be lazy and don't bother with doing an "optional" enhancement and the state of things would be the same as on Windows. Devs are lazy (wll known fact). The blame would be more on lack of evngelizing this new "paradign", or lack of emphasis in the documentation as to how you have to code good MThreaded code, or lack of sample code that gets devs started on this topic (except the super famous BMessage'd boucning balls), or lack of good development tools that would make it easier, but not the pervasive aspect IMHO. But what do I know... Just that when I made the transition from Basic to C or C to C++ I felt roughly as much "increase in expression power" as when I eventually master decently MT'ing after doing only some single-threaded code. An area where single-threadedness makes sense (or at least is used in 99.999% cases) is games though. We still have to see a follow-up to Q3's dual threadedness :-)... But a game takes over the screen and interface by definition, and re-invents the wheel (custom interface, custom widgets ..etc).