News for hackers. Stuff that matters.
Re:Proposal of a new concurrency model for Ruby 3 [pdf] by jph on Thursday September 08, 2016 @02:39AM (#12450758)
The key points IMHO:

1. This Ruby 3 proposal says that Ruby 2 compatibility is mission critical, therefore this proposal rejects concurrency solutions from other languages (e.g. Erlang) and concepts (e.g. functions) and data structures (e.g. immutable collections).

2 Instead the proposal is to create a fast copy-on-write with rules to "deep freeze" some kinds of objects and primitives into an immutable sharable state.

Re:Proposal of a new concurrency model for Ruby 3 [pdf] by nateberkopec on Thursday September 08, 2016 @11:23AM (#12453859)
> This Ruby 3 proposal says that Ruby 2 compatibility is mission critical

Matz has been very public about his fear of a "Python 3" situation occurring in the Ruby community.

Re:Proposal of a new concurrency model for Ruby 3 [pdf] by awj on Thursday September 08, 2016 @11:41AM (#12454036)
And rightly so, I should think. Given the presence of languages like Elixir and Go, creating a situation where you are breaking people's code to introduce multicore programming systems is a pretty bad idea.

I can easily see how people might (rightly or wrongly) say "Ruby 3 broke my code, I'm rewriting in Go".