When One Object Brings Its Whole Family
In object-oriented programming, inheritance lets one kind of object reuse the features of another. A `Banana` class might inherit from a broader `Fruit` class; a program can then use the banana wherever fruit is expected. The convenience can hide a cost: inheriting a class may also make the child depend on behavior and assumptions it does not need.
The “gorilla banana” image captures that surprise. A program asks for a banana, but its design has tied the banana to a gorilla—and perhaps to everything the gorilla needs. In code, those extra pieces may be parent classes, libraries, setup rules, or other objects. The dependency chain can make a small task harder to test, change, or reuse.
Why the Chain Forms
Inheritance is most useful when the relationship is genuinely “is a”: a banana is a fruit, and the fruit’s shared behavior applies to it. Trouble begins when inheritance is used mainly to borrow a convenient feature. The child class then inherits more than the feature, including constraints that may be irrelevant or incompatible.
For example, a class that inherits from a large framework component to gain one formatting method may also require the framework’s configuration and lifecycle. A developer who later changes that component can affect code that seemed unrelated. The original shortcut has turned into coupling: parts of a program are coupled when changes or requirements in one part ripple into another.
Keeping the Banana Small
One alternative is composition: build an object by giving it the specific helper or capability it needs, rather than making it inherit an entire type. A banana object could use a small formatter without becoming a special kind of formatter or depending on a large hierarchy. This makes the relationship explicit and often makes components easier to swap or test.
Inheritance is not inherently a mistake; shared, stable behavior can make it clear and economical. The practical question is whether the child truly belongs to the parent’s category, or merely wants one useful feature. If it is only borrowing, composition can let the program serve the banana without importing the jungle.
