News for hackers. Stuff that matters.
Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by kstenerud on Tuesday January 28, 2020 @03:09PM (#22173548)
What purpose would locks and concurrent primitives have in a system where running code is not preempted?
Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by trhway on Tuesday January 28, 2020 @03:35PM (#22173772)
In addition to parallel in all senses/levels systems mentioned by the other commenter, another example would be a truely single threaded hardware with cooperative or even sequential multithreading where you'd use locking/etc. to safeguard your memory model invariants against for example compiler, JIT and hardware optimization shenanigans.
Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by StillBored on Tuesday January 28, 2020 @07:05PM (#22175640)
To guarantee two different threads don't try to simultaneously mutate (or in some cases access) shared resources.