HTML5 Canvas
Written by: Simon Sarris
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Web Driver
  3. MVVM
  4. REST
  5. ADO.NET
  1. HTML5
  2. Ajax
  3. jQuery Selectors
  4. CSS Part 1
  5. Git

Link Details

Link 1526 thumbnail
User 197663 avatar

By hoskinator
via hoskinator.blogspot.com
Published: Jul 20 2006 / 06:02

Why Interfaces are better than Abstract classes in my opinion of course
  • 13
  • 0
  • 811
  • 1

Comments

Add your comment
User 119725 avatar

Peter Stofferis replied ago:

1 votes Vote down Vote up Reply

Good article although I don't agree with everything: the decision of using inheritance/composition and interface/(abstract)classes should be made depending on the solution you want to reach. I like coding against interfaces because it's an abstraction of the concrete class instances you're using. But I don't implement interfaces for everything, I try to decide if it's needed or not. Interfaces don't make (abstract)classes obsolete. Sometimes you need a combination of both to reach a good solution.

To make things easier I always think of interfaces as the interface/contract and (abstract) classes as the concrete implementation.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.