<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A good example of Abstract class vs Interface</title>
	<atom:link href="http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/</link>
	<description>podcast addict, believes in occam razor, software consultant</description>
	<lastBuildDate>Thu, 02 Feb 2012 23:00:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Levi Page</title>
		<link>http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/comment-page-1/#comment-602</link>
		<dc:creator>Levi Page</dc:creator>
		<pubDate>Wed, 27 Jul 2011 19:34:15 +0000</pubDate>
		<guid isPermaLink="false">/Articles/A-good-example-of-Abstract-class-vs-Interface.aspx#comment-602</guid>
		<description>An abstract class allows polymorphism as well. Not sure why you have it specific to interfaces. To my knowledge, inheriting from multiple classes has nothing to do with polymorphism.</description>
		<content:encoded><![CDATA[<p>An abstract class allows polymorphism as well. Not sure why you have it specific to interfaces. To my knowledge, inheriting from multiple classes has nothing to do with polymorphism.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JP@ classpath in Java</title>
		<link>http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/comment-page-1/#comment-597</link>
		<dc:creator>JP@ classpath in Java</dc:creator>
		<pubDate>Sun, 03 Jul 2011 20:41:28 +0000</pubDate>
		<guid isPermaLink="false">/Articles/A-good-example-of-Abstract-class-vs-Interface.aspx#comment-597</guid>
		<description>Indeed you have done a good job on differentiating the interface and &lt;a href=&quot;http://javarevisited.blogspot.com/2010/10/abstraction-in-java.html&quot; rel=&quot;nofollow&quot;&gt; abstract class in java &lt;/a&gt;. just to add when we use abstract class we can not extend another class but with interface we have that space spare with us. just consider if Runnable were an abstract class instead of interface, how inflexible it would be.&lt;br&gt;&lt;br&gt;Javin&lt;br&gt;&lt;a href=&quot;http://javarevisited.blogspot.com/2011/02/how-hashmap-works-in-java.html&quot; rel=&quot;nofollow&quot;&gt;How HashMap works in Java&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Indeed you have done a good job on differentiating the interface and <a href="http://javarevisited.blogspot.com/2010/10/abstraction-in-java.html" rel="nofollow"> abstract class in java </a>. just to add when we use abstract class we can not extend another class but with interface we have that space spare with us. just consider if Runnable were an abstract class instead of interface, how inflexible it would be.</p>
<p>Javin<br /><a href="http://javarevisited.blogspot.com/2011/02/how-hashmap-works-in-java.html" rel="nofollow">How HashMap works in Java</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/comment-page-1/#comment-219</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 14 Apr 2009 09:31:00 +0000</pubDate>
		<guid isPermaLink="false">/Articles/A-good-example-of-Abstract-class-vs-Interface.aspx#comment-219</guid>
		<description>&lt;p&gt;&quot;The code that we use to love, now doesn&#039;t look as rosy anymore.&quot; &lt;&lt; The speaker&#039;s line was so sweet : )&lt;/p&gt;
&lt;p&gt;Yes Ron, but it was a costly learning curve to me, I had to pay such a huge time for that : (&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>&#8220;The code that we use to love, now doesn&#8217;t look as rosy anymore.&#8221; < < The speaker's line was so sweet : )</p>
</p>
<p>Yes Ron, but it was a costly learning curve to me, I had to pay such a huge time for that : (</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/comment-page-1/#comment-218</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 10 Apr 2009 06:11:00 +0000</pubDate>
		<guid isPermaLink="false">/Articles/A-good-example-of-Abstract-class-vs-Interface.aspx#comment-218</guid>
		<description>&lt;p&gt;@Fajar I was listening to an interesting podcast about legacy code. And the speaker raised something that I found very simple yet profound.&lt;/p&gt;
&lt;p&gt;Legacy code is about perception. As soon as one reaches the next level of craftmanship, suddenly we look back and see our code in a different way. The code that we use to love, now doesn&#039;t look as rosy anymore.&lt;/p&gt;
&lt;p&gt;But hey, that&#039;s the process of learning, right?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Fajar I was listening to an interesting podcast about legacy code. And the speaker raised something that I found very simple yet profound.</p>
<p>Legacy code is about perception. As soon as one reaches the next level of craftmanship, suddenly we look back and see our code in a different way. The code that we use to love, now doesn&#8217;t look as rosy anymore.</p>
<p>But hey, that&#8217;s the process of learning, right?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/comment-page-1/#comment-217</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 09 Apr 2009 08:21:00 +0000</pubDate>
		<guid isPermaLink="false">/Articles/A-good-example-of-Abstract-class-vs-Interface.aspx#comment-217</guid>
		<description>&lt;p&gt;I got this feeling for the first time when I tried to get &quot;Favor composition over inheritance&quot; line from Head First Design Patterns. That means, I even need more than a year to grasp it, how pathetic...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I got this feeling for the first time when I tried to get &#8220;Favor composition over inheritance&#8221; line from Head First Design Patterns. That means, I even need more than a year to grasp it, how pathetic&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.ronaldwidha.net/2008/06/16/a-good-example-of-abstract-class-vs-interface/comment-page-1/#comment-216</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 23 Jul 2008 12:31:00 +0000</pubDate>
		<guid isPermaLink="false">/Articles/A-good-example-of-Abstract-class-vs-Interface.aspx#comment-216</guid>
		<description>&lt;p&gt;Awesome post, very informative.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Awesome post, very informative.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

