<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Thoughts on Parallelism</title>
	<atom:link href="http://enfranchisedmind.com/blog/posts/thoughts-on-parallelism/feed/" rel="self" type="application/rss+xml" />
	<link>http://enfranchisedmind.com/blog/posts/thoughts-on-parallelism/</link>
	<description>programming, politics, &#38; other religious issues</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:16:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Upped The Recent Post/Popular Post Widget Count &#124; Enfranchised Mind</title>
		<link>http://enfranchisedmind.com/blog/posts/thoughts-on-parallelism/#comment-33663</link>
		<dc:creator>Upped The Recent Post/Popular Post Widget Count &#124; Enfranchised Mind</dc:creator>
		<pubDate>Tue, 12 Aug 2008 19:31:50 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2007/02/08/191#comment-33663</guid>
		<description>[...] Thoughts on Parallelism [...]</description>
		<content:encoded><![CDATA[<p>[...] Thoughts on Parallelism [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://enfranchisedmind.com/blog/posts/thoughts-on-parallelism/#comment-33207</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Tue, 13 May 2008 00:38:12 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2007/02/08/191#comment-33207</guid>
		<description>Actually, I disagree that this is a difference.  To tell which locks are &quot;hot&quot;, the lock implementation needs to be modified to keep track of which locks are being contended for.  In much the same way, the STM implementation knows which ref cell caused the conflict that aborted the transaction, and this information could be recorded.  This gives you exactly the same information- where are the contentions?

More generaly, you have to get it right before you make it fast.  I don&#039;t care how fast your program returns the wrong answer.  Locks, especially locks plus mutable data, makes things very hard to get right.  STM, especially STM + strong static typing + purely functional language, makes it very easy to get things right.</description>
		<content:encoded><![CDATA[<p>Actually, I disagree that this is a difference.  To tell which locks are &#8220;hot&#8221;, the lock implementation needs to be modified to keep track of which locks are being contended for.  In much the same way, the STM implementation knows which ref cell caused the conflict that aborted the transaction, and this information could be recorded.  This gives you exactly the same information- where are the contentions?</p>
<p>More generaly, you have to get it right before you make it fast.  I don&#8217;t care how fast your program returns the wrong answer.  Locks, especially locks plus mutable data, makes things very hard to get right.  STM, especially STM + strong static typing + purely functional language, makes it very easy to get things right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raoul Duke</title>
		<link>http://enfranchisedmind.com/blog/posts/thoughts-on-parallelism/#comment-33182</link>
		<dc:creator>Raoul Duke</dc:creator>
		<pubDate>Sat, 10 May 2008 00:07:59 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2007/02/08/191#comment-33182</guid>
		<description>A smart acquaintance hilighted recently to me one seemingly large problem with STM vs. locks: at least with locks it is obvious which ones are &quot;hot&quot; so you can improve performance. With a transaction (whatever the connotation) if you get rollback you do not know why. So you can&#039;t rework your code to avoid it in the future so easily.</description>
		<content:encoded><![CDATA[<p>A smart acquaintance hilighted recently to me one seemingly large problem with STM vs. locks: at least with locks it is obvious which ones are &#8220;hot&#8221; so you can improve performance. With a transaction (whatever the connotation) if you get rollback you do not know why. So you can&#8217;t rework your code to avoid it in the future so easily.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enfranchised Mind &#187; Functional Language Adoption</title>
		<link>http://enfranchisedmind.com/blog/posts/thoughts-on-parallelism/#comment-31149</link>
		<dc:creator>Enfranchised Mind &#187; Functional Language Adoption</dc:creator>
		<pubDate>Thu, 28 Jun 2007 12:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2007/02/08/191#comment-31149</guid>
		<description>[...] is the continuation of a conversation started at Brian&#8217;s post on approaches to parallelism infrastructure, and continued at Thinking [...]</description>
		<content:encoded><![CDATA[<p>[...] is the continuation of a conversation started at Brian&#8217;s post on approaches to parallelism infrastructure, and continued at Thinking [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thinking Parallel &#187; Blog Archive &#187; News for Week 25/2007</title>
		<link>http://enfranchisedmind.com/blog/posts/thoughts-on-parallelism/#comment-31115</link>
		<dc:creator>Thinking Parallel &#187; Blog Archive &#187; News for Week 25/2007</dc:creator>
		<pubDate>Wed, 20 Jun 2007 14:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2007/02/08/191#comment-31115</guid>
		<description>[...] are going even further down memory lane with this post on Enfranchised Mind about Parallelism in General. It feels good to see a well-balanced and thought [...]</description>
		<content:encoded><![CDATA[<p>[...] are going even further down memory lane with this post on Enfranchised Mind about Parallelism in General. It feels good to see a well-balanced and thought [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

