NOTE: This article was one of many content experiments published in Volume 6, which aimed to try out different formats and styles to see what readers thought of them.
In many of our articles, I have attempted to discuss the question of code reuse in Ruby (particularly composition vs. inheritance), but have found it difficult to express these ideas in our traditional format. Ruby’s code sharing semantics cannot be easily expressed in a simple linear story arc, so a more formal style might help reveal the deeply interconnected concepts that make up this topic.
Because it fits the structure a bit better, I’ve rendered this article in PDF format. Please download the document and let me know what you think!
Practicing Ruby is proudly independent, open source, and advertising-free.
This is a 100% reader-funded, reader-focused project that needs your support.