On: 2012: The year Rubyists learned to stop worrying a...

[fzzzy]

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.

[bascule → fzzzy]

Only one of the proposals had anything to do with immutability

[fzzzy → bascule]

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.