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 select on events - Yes, please do it! That will be a big help for all kinds
of applications, aside from singlethreaded loop dispatching. DEC VMS had a
"logical event flag" for that, if I remember right after all these years, just
a one bit value that the caller optionally supplies with a long system request.
Re multithreaded application architectures - how could you get optimal performance
with a browser with less than one rendering thread per window? If each rendering
window has its own thread, then when one is hanging on disk I/O or something, another
can run. But single threaded, it's just dead time. A single slave thread handling
it for the whole application isn't going to add any performance.
Re select on events - Yes, please do it! That will be a big help for all kinds of applications, aside from singlethreaded loop dispatching. DEC VMS had a "logical event flag" for that, if I remember right after all these years, just a one bit value that the caller optionally supplies with a long system request. Re multithreaded application architectures - how could you get optimal performance with a browser with less than one rendering thread per window? If each rendering window has its own thread, then when one is hanging on disk I/O or something, another can run. But single threaded, it's just dead time. A single slave thread handling it for the whole application isn't going to add any performance.