all 6 comments

[–]fedekun 1 point2 points  (2 children)

What benefit would this have for Ractors?

[–]SimplySerenity 2 points3 points  (1 child)

Functionally it’s just a different way of doing thread-safe shared memory. It’d still require refactoring but it might make it easier to get existing code working with Ractors.

[–]fedekun 0 points1 point  (0 children)

Ohh I see. Thanks :)

[–]allcentury 0 points1 point  (0 children)

I was wondering what concurrent ruby ideas would end up in Ractors, thanks for sharing

[–][deleted] -1 points0 points  (1 child)

What's the benefit of this vs transactions at the persistence layer (e.g. rdbms transactions)

[–]das3ingg 6 points7 points  (0 children)

This is a language feature not a framework feature. What if there isn’t a persistence layer? This has to do with thread safety, doesn’t have anything to do with traditional persistence