Get the latest tech news

Ruby 3.5 Feature: Namespace on read


Redmine

I understand wanting to merge soon to avoid conflicts but also there hasn't been a proper discussion on the advantages of Namespace vs sub-interpreters (which could have started long before the implementation was near-complete). Given that TruffleRuby and JRuby and many other VMs have sub-interpreters, I think it's crucial to figure out if it's worth doing something different like Namespace (which can't run in parallel, has weaker isolation, has more overhead, etc, so seems worse in most aspects). It is the combination of isolation + constant access outside the namespace + method call semantics that I find difficult to reconcile (does not mean it is impossible with newly introduced rules).

Get the Android app

Or read this on Hacker News

Read more on:

Photo of Feature

Feature

Photo of Read

Read

Photo of ruby

ruby

Related news:

News photo

iOS 19 may bring a feature that makes signing into public Wi-Fi less of a hassle

News photo

An Introduction to Solid Queue for Ruby on Rails

News photo

Show HN: A backend agnostic Ruby framework for building reactive desktop apps