<?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: Twitter in Scala</title>
	<atom:link href="http://www.sauria.com/blog/2007/05/04/twitter-in-scala/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sauria.com/blog/2007/05/04/twitter-in-scala/</link>
	<description>Open Source, Modern Programming Languages, OS X, Photography, and ...</description>
	<pubDate>Fri, 05 Dec 2008 14:06:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: rick</title>
		<link>http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4718</link>
		<dc:creator>rick</dc:creator>
		<pubDate>Mon, 07 May 2007 19:24:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4718</guid>
		<description>(sorry, I couldn't resist.)  I'm willing to look at Scala next.
As far as typing - I appreciate both approaches - but static typing to me seems to help eliminate a whole class of human errors during development of large systems. Without them, complete coverage of the runtime seems to be required just to rule out simple mistakes. (I see enough JavaScript errors popup on web pages regularly to realize this is a common affliction!)</description>
		<content:encoded><![CDATA[<p>(sorry, I couldn&#8217;t resist.)  I&#8217;m willing to look at Scala next.<br />
As far as typing - I appreciate both approaches - but static typing to me seems to help eliminate a whole class of human errors during development of large systems. Without them, complete coverage of the runtime seems to be required just to rule out simple mistakes. (I see enough JavaScript errors popup on web pages regularly to realize this is a common affliction!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc&#8217;s Voice &#187; Blog Archive &#187; Twitter clone</title>
		<link>http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4686</link>
		<dc:creator>Marc&#8217;s Voice &#187; Blog Archive &#187; Twitter clone</dc:creator>
		<pubDate>Mon, 07 May 2007 06:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4686</guid>
		<description>[...] I&#8217;ve been thinking about what I don&#8217;t like about Twitter and I just saw this post from Ted Leung about a Twitter clone. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve been thinking about what I don&#8217;t like about Twitter and I just saw this post from Ted Leung about a Twitter clone. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Leung</title>
		<link>http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4537</link>
		<dc:creator>Ted Leung</dc:creator>
		<pubDate>Sat, 05 May 2007 00:34:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4537</guid>
		<description>In the words of Alan Kay "I’m not against types, but I don’t know of any type systems that aren’t a complete pain, so I still like dynamic typing."  The jury is out on whether Scala's type system is a complete pain or not.

Dude, I tried to persuade you guys to study Scala earlier this year...</description>
		<content:encoded><![CDATA[<p>In the words of Alan Kay &#8220;I’m not against types, but I don’t know of any type systems that aren’t a complete pain, so I still like dynamic typing.&#8221;  The jury is out on whether Scala&#8217;s type system is a complete pain or not.</p>
<p>Dude, I tried to persuade you guys to study Scala earlier this year&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rick</title>
		<link>http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4535</link>
		<dc:creator>rick</dc:creator>
		<pubDate>Sat, 05 May 2007 00:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2007/05/04/twitter-in-scala/#comment-4535</guid>
		<description>this is very cool - and I can see it being more deployable in an environment with existing services (being JVM-based.) But you do realize that its strongly-typed don't you?</description>
		<content:encoded><![CDATA[<p>this is very cool - and I can see it being more deployable in an environment with existing services (being JVM-based.) But you do realize that its strongly-typed don&#8217;t you?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
