Post #2053447
2025-11-03 18:57 UTC
I figured out why I don't like Ruby's new Ractor concept: it forces users to work around CRuby deficiencies. To parallelize code with Ractor, users must make all passed object graphs "shareable" even if those objects would otherwise be safe to parallelize with Threads. It feels un-Ruby to me.
Replies (1)
-
@headius@mastodon.social 2025-11-03 19:04
As proof of this: JRuby and TruffleRuby can already parallelize Threads. You can prefer immutable shared state, but you can also manage your own mutable shared state and still get parallelism. You can’t do the latter with Ractors *solely* because CRuby is unable to support that.