Re:2012: The year Rubyists learned to stop worrying and love...
by tel on Tuesday December 18, 2012 @07:42PM
(#4940582)
I don't want to be "that Haskell guy" but that's all I could read from this. Realistic multithreading and immutability are deeply tied. I'm very interested to see how far the MRI community can come to getting decent multithreading by implementing suggestions such as these... since my learned intuition is to just throw out mutability and plan in that, much simpler and more limited, sandbox.
[ Parent
| on HN ]
Re:2012: The year Rubyists learned to stop worrying and love...
by fzzzy on Wednesday December 19, 2012 @01:01AM
(#4941392)
It's funny, the article doesn't really even contain anything about threading. It just has a bunch of band-aid solutions to tack on immutable message passing on top of global mutable shared state.
Re:2012: The year Rubyists learned to stop worrying and love...
by bascule on Wednesday December 19, 2012 @01:39AM
(#4941462)
Only one of the proposals had anything to do with immutability
Re:2012: The year Rubyists learned to stop worrying and love...
by fzzzy on Friday December 21, 2012 @03:04AM
(#4951933)
Huh? Deep Freeze, Deep Dup, and Ownership Transfer are all strategies to avoid multiple concurrent actors mutating the same objects at the same time.
Even the last proposal, which I think has to do with fine grained locking, is still a strategy to avoid issues with mutable shared state.