Comments on: Interface vs Abstract Class

By: artist studio ,gallery, paintings,Indian art, abstract, expressionistic,art

artist studio ,gallery, paintings,Indian art, abstract, expressionistic,art — Sun, 27 Nov 2011 17:42:25 +0000

Great items from you, man. I’ve be aware your stuff prior to and you’re just extremely excellent. I actually like what you have bought right here, really like what you’re stating and the best way through which you assert it. You’re making it enjoyable and you still care for to keep it smart. I can’t wait to read much more from you. That is really a tremendous website.

By: ajay

ajay — Sat, 29 Oct 2011 17:05:34 +0000

wola…!
after spending almost half hour on the net. i found this article. it clearly shows the difference between the both.

By: pavel

pavel — Tue, 13 Sep 2011 10:13:56 +0000

The abstract classes and interfaces exist in OO languages and are semantically separated for a very good reason – software design. The question “Interface vs Abstract class?” is menanigless. Good software designer will not ask such questions as usage scenarios for interfaces are very different from those of the abstract classes and aren’t supposed to be interchangeable if we are to preserve the good design. It is not a coincidence the interface is named “inter” (between) + “face” (exposed) – it is the public face of whatever component/class implements it. The abstract classes on the other hand tend to hold specific implementation details and merely act as a common base for a given class hierarchy. Furthermore, it is not uncommon in the complex software systems, for abstract classes to implement interfaces by providing some common/shared implementation and allowing concrete classes to further deal with the specifics …

By: Jaykishan Parikh

Jaykishan Parikh — Mon, 14 Jun 2010 07:31:49 +0000

interface describes “What to do” but does not have anything like “How to do”. It is the responsibility of implementer to how to do.

In early stage of your design, You are not clear with how to implement the things but you are very much sure about what to do. So interface should be used.

In case you are some how clear with the implementation then use abstract class where you make concrete methods for which you know hoe to implement, and keep other methods as abstract to let derived class to implement them.

By: Interface vs Abstract Class | TechArtifact interface

Interface vs Abstract Class | TechArtifact interface — Sat, 12 Sep 2009 12:18:18 +0000

[...] Originally posted here: Interface vs Abstract Class | TechArtifact [...]

By: Jennifer

Jennifer — Fri, 21 Aug 2009 07:19:54 +0000

Thanks for the nice article and I absolutely agree with Jetspeed’s statement. Those who think something is misleading shud prove their way of thinking else stop spamming.

By: Jetspeed

Jetspeed — Mon, 17 Aug 2009 10:48:27 +0000

Well i am surprised to see comment of Mr Sagar. Where does this article is mis-leading. I agree this article doesn’t contain all the information about abstract & interface, IMO it is not possible to cover every single aspect of any technology in single blog post, but It doesn’t mean it is contain some “superficial knowledge”.

i think you should appreciate vinay’s effort in putting up all this.
If you think information is “superficial knowledge” please post a link here. I think Vinay would be happy to update the post.

By: Ankit Goyal

Ankit Goyal — Mon, 17 Aug 2009 10:09:32 +0000

@sagar
Can u give us the correct version of the statement u are saying as wrong??

By: Pravin

Pravin — Sat, 15 Aug 2009 01:57:50 +0000

Abstract classes are not faster than interfaces. Only
final methods could be faster depending on JVM implementation.

By: Roger vd Kimmenade

Roger vd Kimmenade — Mon, 10 Aug 2009 18:42:08 +0000

I agree with Urs Enzler, interfaces give you far more flexibility (for example by the use of the Dependency Injection pattern). Furthermore the performance is always a debate. Interfaces keeps the software manageable.

Btw what has this topic to do with Service Oriented Architecture? Maybe include Abstract Class vs Interface vs Service Contract?