I can't reply to you directly. I didn't mean to imply that TempleOS is not multiprocessing. From what I gather there is only one user (with multiple processes) and that user owns all the files, hence no file permissions that say "this file belongs to user X" and "this file belongs to user Y", only user X can read/write/execute X's files, and the same for user Y. The author of the article linked to here states that TempleOS is a single user (but multiprocess!) system.
I wonder why you haven't implemented threads? Not enough of a benefit in your opinion? Aren't threads supported by modern CPUs. Don't they allow faster context switching than switching context for processes? Though I guess Erlang disagrees!
There's no memory protection, so like for other multitasking systems without memory protection (like AmigaOS...) the process/thread distinction doesn't matter.
I can't reply to you directly. I didn't mean to imply that TempleOS is not multiprocessing. From what I gather there is only one user (with multiple processes) and that user owns all the files, hence no file permissions that say "this file belongs to user X" and "this file belongs to user Y", only user X can read/write/execute X's files, and the same for user Y. The author of the article linked to here states that TempleOS is a single user (but multiprocess!) system.
I wonder why you haven't implemented threads? Not enough of a benefit in your opinion? Aren't threads supported by modern CPUs. Don't they allow faster context switching than switching context for processes? Though I guess Erlang disagrees!