<?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"
	>
<channel>
	<title>Comments on: Dead Duck Typing and High Cohesion</title>
	<atom:link href="http://www.pathf.com/blogs/2007/12/dead-duck-typin/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2007/12/dead-duck-typin/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Wed, 15 Oct 2008 21:29:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: T.J.</title>
		<link>http://www.pathf.com/blogs/2007/12/dead-duck-typin/#comment-156</link>
		<dc:creator>T.J.</dc:creator>
		<pubDate>Fri, 28 Dec 2007 23:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=127#comment-156</guid>
		<description>&lt;p&gt;Good post.  Programmers will happily point out language a != language b or language c &gt;language a, but when it comes down to OO practices, the ideology is the essentially the same.  Ruby is a relatively new language (at least in the mainstream), so expect more and more object orientation in newer releases.  PHP finally got some decent OO structure, I expect Ruby to follow.&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Good post.  Programmers will happily point out language a != language b or language c >language a, but when it comes down to OO practices, the ideology is the essentially the same.  Ruby is a relatively new language (at least in the mainstream), so expect more and more object orientation in newer releases.  PHP finally got some decent OO structure, I expect Ruby to follow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
