title: Should inheritance (of non-interface types) be removed from programming languages?
body: <p>This is quite a controversial topic, and before you say "no", is it really, really needed?    </p>
  
  <p>I have been programming for about 10 years, and I can't honestly say that I can recall a time where inheritance solved a problem that couldn't be solved another way.  On the other hand I can recall many times when I used inheritance, because I felt like I had to or because I though I was clever and ended up paying for it.</p>
  
  <p>I can't really see any circumstances where, from an implementation stand point, aggregation or another technique could not be used instead of inheritance.  </p>
  
  <p>My only caveat to this is that we would still allow inheritance of interfaces.</p>
  
  <p>(Update)</p>
  
  <p>Let's give an example of why it's needed instead of saying, "sometimes it's just needed."  That really isn't helpful at all.  Where is your proof?</p>
  
  <p>(Update 2 Code Example)</p>
  
  <p>Here's the classic shape example, more powerful, and more explicit IMO, without inheritance.  It is almost never the case in the real world that something really "Is a" of something else.  Almost always "Is Implemented in Terms of"  is more accurate.</p>
  
  <pre><code>public interface IShape
  {
      void Draw();
  }
  
  public class BasicShape : IShape
  {
      public void Draw()
      {
          // All shapes in this system have a dot in the middle except squares.
          DrawDotInMiddle();
      }
  }
  
  public class Circle : IShape
  {
      private BasicShape _basicShape;
  
      public void Draw()
      {
          // Draw the circle part
          DrawCircle();
          _basicShape.Draw();
      }
  }
  
  public class Square : IShape
  {
      private BasicShape _basicShape;
  
      public void Draw()
      {
          // Draw the circle part
          DrawSquare();
      }
  }
  </code></pre>