Threads Are a Bad Idea for Most Purposes (1995) [pdf]

Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by harikb on Tuesday January 28, 2020 @04:22PM (#22174184)

If we read other people’s (say a manager, who is giving work) mind and just did that, we would be in the exact mess we are with shares mutable state.

[ Parent | on HN ]

Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by SeekingMeaning on Tuesday January 28, 2020 @05:30PM (#22174817)

Imagine reading someone else’s mind, only to discover that they are reading yours... Mind-stack overflow?

[ Parent | on HN ]

Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by derefr on Tuesday January 28, 2020 @06:54PM (#22175540)

for certain classes of problems, sure. But how about “embarrassingly parallel” jobs (e.g. weeding a garden) or even “idempotent OLTP” jobs (e.g. studying several subjects at once)?

(Technically these aren’t best expressed as SHM but rather as a tuplespace or greedy worker-pool abstraction, but they can be achieved starting off with “just” an SHM threading primitive, so they count, I think.)

[ Parent | on HN ]