News for hackers. Stuff that matters.
Re:A Constructive Look at TempleOS by igravious on Monday June 08, 2015 @07:21PM (#9683132)
Read the article :) Not multi-user. No networking.
Re:A Constructive Look at TempleOS by igravious on Monday June 08, 2015 @07:39PM (#9683194)
Hi Terry,

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!

Re:A Constructive Look at TempleOS by kragen on Monday June 08, 2015 @11:25PM (#9683917)
> I wonder why you haven't implemented threads?

What TempleOS calls “processes” is what you are used to calling “threads”.

Re:A Constructive Look at TempleOS by vidarh on Monday June 08, 2015 @07:52PM (#9683242)
There's no memory protection, so like for other multitasking systems without memory protection (like AmigaOS...) the process/thread distinction doesn't matter.
Re:A Constructive Look at TempleOS by TerryADavis on Monday June 08, 2015 @07:25PM (#9683146)
It is multiprocessing, but not fair sharing. I like to call it single-process multiple thread. There is no difference between "task", "Process" or "thread". It is single address map. Paging in not used, basically.
Re:A Constructive Look at TempleOS by vidarh on Monday June 08, 2015 @09:06PM (#9683499)
I don't think many people today realise how profoundly this can affect an OS (despite the many challenges). AmigaOS was the same, and it allowed a lot of hacks that are much more challenging to replicate in efficient ways on more modern OSs.
Re:A Constructive Look at TempleOS by k__ on Monday June 08, 2015 @08:39PM (#9683427)
Why are all, but this comment of you, [dead]?
Re:A Constructive Look at TempleOS by orionblastar on Monday June 08, 2015 @08:56PM (#9683472)
I think an admin has to approve his comments because he has been shadowbanned.

In the past he made racist and homophobic remarks and got shadowbanned. His mental illness is hard to understand at times. The same thing happened to him on Reddit. He has to use multiple accounts to get around the shadowbans.

I think he is like Brandon Eich who donated to the wrong charity, made good contributions and solid programming work, but holds opinions that are not socially acceptable.

Re:A Constructive Look at TempleOS by oofabz on Tuesday June 09, 2015 @12:05AM (#9684015)
>Brandon Eich

I'd take HolyC over Javascript any day.

Re:A Constructive Look at TempleOS by pygy_ on Monday June 08, 2015 @08:52PM (#9683465)
The admins said a few months ago that they would add the possibility for high-karma users to unban select post of shadow banned accounts.

It might have landed (either in closed beta or I don't have enough karma to do it). Or maybe it was simply revived by an admin...

Re:A Constructive Look at TempleOS by chomp on Monday June 08, 2015 @07:47PM (#9683222)
Terry,

You are currently shadow banned.

Re:A Constructive Look at TempleOS by rosser on Monday June 08, 2015 @08:11PM (#9683329)
He knows this already.
Re:A Constructive Look at TempleOS by pygy_ on Monday June 08, 2015 @08:06PM (#9683309)
Not anymore, apparently. At least the post I suppose you couldn't reply to in this thread isn't [dead] right now. Another comment of his still is.