<?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: Scottish Programming Languages Seminar</title>
	<atom:link href="http://www.nobugs.org/blog/archives/2005/07/03/scottish-programming-languages-seminar/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nobugs.org/blog/archives/2005/07/03/scottish-programming-languages-seminar/</link>
	<description>Thoughts of a software engineer</description>
	<pubDate>Tue, 06 Jan 2009 15:27:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Eugene Wallingford</title>
		<link>http://www.nobugs.org/blog/archives/2005/07/03/scottish-programming-languages-seminar/#comment-3240</link>
		<dc:creator>Eugene Wallingford</dc:creator>
		<pubDate>Fri, 08 Jul 2005 19:58:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.nobugs.org/blog/?p=123#comment-3240</guid>
		<description>Thanks for the summary.  I wish I could go to more seminars of this sort, but they are scarce in my immediate neighborhood.  Reading about them is the next best thing to being there!

On measuring the productivity difference between static and dynamic languages:  I agree wholeheartedly.  The difference is more of culture and thought habit than of tools, and measuring productivity across cultures is tricky.  Folks just end up thinking, "But that's not even a part of my universe."

"The formal side of this talk was a little bit beyond me.  I have to concentrate when people discuss Monads formally."

I have to admit, with some sheepishness, that reading and listening about monads makes my head hurt. :-)

On type-checking as good versus bad:  Again, I agree -- vehemently.  The presumption of strongly, statically typed languages is that the first step toward being a good program is passing the type checker.  This is potentially a very fine assertion, but it has implications for how people think about programs and programming.  What if we decided that the first step toward being a good program was something else and designed a tool to enforce this notion?  Programming might be quite different!  I think that test-driven development is an example of just this sort of thing.</description>
		<content:encoded><![CDATA[<p>Thanks for the summary.  I wish I could go to more seminars of this sort, but they are scarce in my immediate neighborhood.  Reading about them is the next best thing to being there!</p>
<p>On measuring the productivity difference between static and dynamic languages:  I agree wholeheartedly.  The difference is more of culture and thought habit than of tools, and measuring productivity across cultures is tricky.  Folks just end up thinking, &#8220;But that&#8217;s not even a part of my universe.&#8221;</p>
<p>&#8220;The formal side of this talk was a little bit beyond me.  I have to concentrate when people discuss Monads formally.&#8221;</p>
<p>I have to admit, with some sheepishness, that reading and listening about monads makes my head hurt. <img src='http://www.nobugs.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>On type-checking as good versus bad:  Again, I agree &#8212; vehemently.  The presumption of strongly, statically typed languages is that the first step toward being a good program is passing the type checker.  This is potentially a very fine assertion, but it has implications for how people think about programs and programming.  What if we decided that the first step toward being a good program was something else and designed a tool to enforce this notion?  Programming might be quite different!  I think that test-driven development is an example of just this sort of thing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
