<?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: monotonous</title>
	<atom:link href="http://joeshaw.org/2007/10/28/496/feed" rel="self" type="application/rss+xml" />
	<link>http://joeshaw.org/2007/10/28/496</link>
	<description></description>
	<lastBuildDate>Wed, 18 Mar 2009 16:01:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: thomas.apestaart.org &#187; strongly typed</title>
		<link>http://joeshaw.org/2007/10/28/496/comment-page-1#comment-320936</link>
		<dc:creator>thomas.apestaart.org &#187; strongly typed</dc:creator>
		<pubDate>Mon, 29 Oct 2007 08:49:43 +0000</pubDate>
		<guid isPermaLink="false">http://joeshaw.org/2007/10/28/496#comment-320936</guid>
		<description>[...] But to keep it technical, I read through his reply to some Beagle comments, which resonated with me:  And lastly, having worked with Trow on a reasonably big desktop Python app, we wanted a strongly typed language. Writing real applications in Python requires a discipline that unfortunately most people (including myself) are unwilling to adhere to, and this easily leads to buggy and hard to maintain programs. You have to be very diligent about unit tests and code coverage for every line of code, because you can’t rely on the compiler to catch errors for you. We had been burned by this a bit, and wanted to get back to a strongly typed, but still easy to use language that integrated well with the desktop. [...]</description>
		<content:encoded><![CDATA[<p>[...] But to keep it technical, I read through his reply to some Beagle comments, which resonated with me:  And lastly, having worked with Trow on a reasonably big desktop Python app, we wanted a strongly typed language. Writing real applications in Python requires a discipline that unfortunately most people (including myself) are unwilling to adhere to, and this easily leads to buggy and hard to maintain programs. You have to be very diligent about unit tests and code coverage for every line of code, because you can’t rely on the compiler to catch errors for you. We had been burned by this a bit, and wanted to get back to a strongly typed, but still easy to use language that integrated well with the desktop. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
