> What's the theoretical alternative? Adding stuff to a global interpreter state is the goal. This is the right way to do it but it suffers from a lack of corr

> What's the theoretical alternative? Adding stuff to a global interpreter state is the goal. This is the right way to do it but it suffers from a lack of correct tooling. The Self[0] programming environment assigns a "module" to each "slot" (class methods in Ruby land); an object may be composed from multiple modules at once. If Ruby had this kind of granularity in its inclusion system I believe that a lot of the confusion around where a particular method comes from would disappear. [0]: https://selflanguage.org/ https://selflanguage.org/