Travis Swicegood has made two
blog posts about his agreement with other statements made about why class inheritance sucks.
From the
original comments made by
Bernard Sumption:
All of the pain caused by inheritance can be traced back to the fact that inheritance forces 'is-a' rather than 'has-a' relationships. If class R2Unit extends Droid, then a R2Unit is-a Droid. If class Jedi contains an instance variable of type Lightsabre, then a Jedi has-a Lightsabre.
Travis agrees and then comes back with his
second post to clarify something - composition versus inheritance:
I approach OOP from a flexibility standpoint with one of its biggest flex-points being loose coupling which in turn promotes reusability. I'm going to use Event as a hypothetical example.
He uses Events and design pattern illustrations (like the Visitor and Observer) to help illustrate his point.
Travis Swicegood's Blog: Why Inheritance Sucks - Read More... 
