Copied from the answer I made for the closed question "What is / was so amazing with respect to BeOS [closed]", but it is very well applied here:
The strange thing about developing BeOS from memory is that the graphical interface is really multithreaded, unlike graphical interfaces on other platforms that tend to be completely single-threaded.
This meant that the GUI application development for BeOS was completely different, but I guess it meant that the GUI was more responsive without requiring explicit application-level design to interact with the GUI.
Of course, this means using mutexes, etc. more important, and transferring graphical applications from another OS to BeOS is difficult if the BeOS GUI library does not turn into a single-threaded library using and using one system-wide mutex.
Linux, Windows, and almost all other OSs, I can come up with the idea that I have used multithreading support in recent decades, Linux and Windows, which use multithreading in different ways, but do it very well - however BeOS does use multithreading everywhere - and it becomes obvious. for example, in the GUI structure, while most others are strictly single-threaded. (Or, as a last resort, allow multiple threads access with the consequences of undefined ...)
Arafangion
source share