News for hackers. Stuff that matters.
Re:Ruby's Proposed STM by taffer on Friday October 30, 2020 @05:32AM (#24940544)
Threads are fine as long as they do not share mutable data structures. For example, multithreaded application servers are a rather painless experience.
Re:Ruby's Proposed STM by eyelidlessness on Friday October 30, 2020 @10:54AM (#24942850)
Since all of these concurrency approaches’ pain points are around shared mutable state, maybe it’s shared mutable state that’s the pain point.
Re:Ruby's Proposed STM by bglusman on Friday October 30, 2020 @11:37AM (#24943338)
Yup, this is the conclusion of Joe Armstrong and why Erlang/Elixir/BEAM just doesn't allow mutable state, other than process dictionary which is inherently non-shared.
Re:Ruby's Proposed STM by mumblemumble on Friday October 30, 2020 @09:16AM (#24941885)
That observation doesn't really contribute to a comparison of dedicated threads and async/await, though, because the same is true of async routines.