<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>Comments for page &quot;Performance Economics&quot;</title>
		<link>http://syntax.wikidot.com/blog:10/comments/show</link>
		<description></description>
				<copyright></copyright>
		<lastBuildDate>Sun, 26 May 2013 02:34:14 +0000</lastBuildDate>
		
					<item>
				<guid>http://syntax.wikidot.com/blog:10/comments/show#post-392000</guid>
				<title>Re:</title>
				<link>http://syntax.wikidot.com/blog:10/comments/show#post-392000</link>
				<description></description>
				<pubDate>Sat, 21 Feb 2009 14:24:49 +0000</pubDate>
				<wikidot:authorName>gar</wikidot:authorName>				<wikidot:authorUserId>21583</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p>Hi Luke</p> <p>"But comparing a C compiler and a Haskell compiler is like comparing Babe Ruth to Pele." I was thinking more along the lines of a chain saw and an Intergalactic Telefunctor. ;)</p> <p>"I don't know how popular computer science has adopted such a nonscientific culture." I'm willing to bet the marketing department had something to do with it. Just a hunch.</p> <p>It <em>would</em> be useful to have a bona-fide economic analysis of the costs/benefits associated with the two styles of programming, but you'd have to have a combination economist/computer scientist to do it. For example, testing and bug fixing has a direct cost, but also an indirect cost of lost opportunity - time spent hunting down and fixing bugs could be spent improving the product. It would be interesting to see real (or at least principaled) numbers. I suppose eventually, once the real money starts flowing towards FPLs, we'll see something like that.</p> <p>Sorry about the 30 character thing. I'll file a bug report.</p> <p>Thanks,</p> <p>-gregg</p> 
				 	]]>
				</content:encoded>							</item>
					<item>
				<guid>http://syntax.wikidot.com/blog:10/comments/show#post-391977</guid>
				<title>(no title)</title>
				<link>http://syntax.wikidot.com/blog:10/comments/show#post-391977</link>
				<description></description>
				<pubDate>Sat, 21 Feb 2009 13:35:50 +0000</pubDate>
				<wikidot:authorName>Luke Palmer</wikidot:authorName>								<content:encoded>
					<![CDATA[
						 <p>I like your thesis.</p> <p>The "ghc vs. gcc" discussion is silly, and flame wars derived from such a comparison perpetuate harmful patterns of thought. <em>Maybe</em> it is possible to compare two C compilers objectively and say that one is better than the other, but you'd need a lot of evidence. But comparing a C compiler and a Haskell compiler is like comparing Babe Ruth to Pele.</p> <p>gcc when given input A produced code which ran in less time than ghc when given input B. But we have no theory telling us that A and B are the same program; simply that they print the same number when run. But I can write C (and Haskell) programs which are much faster and much slower than that benchmark, which print the same number.</p> <p>This difference isn't purely academic, however. I bet that I can write a lambda calculus interpreter in Haskell which a C programmer would be hard-pressed to compete with. People want fast lambda calculus interpreters; such cannot be said for programs which print out some arbitrary fixed number.</p> <p>I hate language shootouts, benchmarks between languages. Speed is not a property of a language, it is a property of a <em>program</em>. Unless you can show that two programs are the same (intensionally!), comparisons are meaningless. And even if you do show that they are the same, your comparison has correctly compared the speed of the compiler for <em>one</em> input.</p> <p>I don't know how popular computer <em>science</em> has adopted such a nonscientific culture.</p> <div class="code"> <pre> <code>&lt;/rant&gt;</code> </pre></div> <p>(Oh, also, whose bright idea was it to restrict the website field in your blog to 30 characters? :-)</p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>