<?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 for And I thank God for...</title>
	<atom:link href="http://mtfulmer.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://mtfulmer.wordpress.com</link>
	<description>Matthew Fulmer's Personal Journal</description>
	<pubDate>Thu, 24 Jul 2008 22:22:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>Comment on E Concurrency model by Three ways to Parallelize a Raytracer &#171; And I thank God for&#8230;</title>
		<link>http://mtfulmer.wordpress.com/2008/03/21/e-concurency-model/#comment-1045</link>
		<dc:creator>Three ways to Parallelize a Raytracer &#171; And I thank God for&#8230;</dc:creator>
		<pubDate>Tue, 08 Jul 2008 23:08:23 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/?p=19#comment-1045</guid>
		<description>[...] well the approach maps to the  E Concurrency model , which I also call the vat model, [...]</description>
		<content:encoded><![CDATA[<p>[...] well the approach maps to the  E Concurrency model , which I also call the vat model, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on E Concurrency model by Toby</title>
		<link>http://mtfulmer.wordpress.com/2008/03/21/e-concurency-model/#comment-1039</link>
		<dc:creator>Toby</dc:creator>
		<pubDate>Fri, 21 Mar 2008 15:22:04 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/?p=19#comment-1039</guid>
		<description>Another good reference is Mark  Miller's &lt;a href="http://www.erights.org/talks/thesis/" rel="nofollow"&gt;Phd Thesis&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Another good reference is Mark  Miller&#8217;s <a href="http://www.erights.org/talks/thesis/" rel="nofollow">Phd Thesis</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on E Concurrency model by Ron Welch</title>
		<link>http://mtfulmer.wordpress.com/2008/03/21/e-concurency-model/#comment-1038</link>
		<dc:creator>Ron Welch</dc:creator>
		<pubDate>Fri, 21 Mar 2008 15:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/?p=19#comment-1038</guid>
		<description>Nice work. I am hoping that you will expound on the relationship to Croquet's TeaTime at some point....</description>
		<content:encoded><![CDATA[<p>Nice work. I am hoping that you will expound on the relationship to Croquet&#8217;s TeaTime at some point&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on E Concurrency model by Mark</title>
		<link>http://mtfulmer.wordpress.com/2008/03/21/e-concurency-model/#comment-1037</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Fri, 21 Mar 2008 05:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/?p=19#comment-1037</guid>
		<description>Really good explanation. Thanks!</description>
		<content:encoded><![CDATA[<p>Really good explanation. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should I work on proprietary software? by Patrick Logan</title>
		<link>http://mtfulmer.wordpress.com/2007/01/17/should-i-work-on-proprietary-software/#comment-1033</link>
		<dc:creator>Patrick Logan</dc:creator>
		<pubDate>Wed, 23 Jan 2008 03:33:49 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/2007/01/17/should-i-work-on-proprietary-software/#comment-1033</guid>
		<description>Good post on your deliberations. As someone who worked for Intel for over ten years, here's my two cents...

In this case I think there is some logic to keeping the software internal. There were several situations in my career there where some seemingly innocuous software could divulge to someone information about Intel's business, e.g. it could have divulged, or appeared to, information about fab yields in one case and product orders in some other cases.

In the case of testing products, the software structure itself could divulge information about what Intel is testing, how they're testing, etc. Maybe that's harmless, maybe not. But Intel is a competitive company and has an obligation to its shareholders to protect its interests. Sometimes those interests are served by open source, and sometimes the decision has to be made the other way, hopefully wisely.</description>
		<content:encoded><![CDATA[<p>Good post on your deliberations. As someone who worked for Intel for over ten years, here&#8217;s my two cents&#8230;</p>
<p>In this case I think there is some logic to keeping the software internal. There were several situations in my career there where some seemingly innocuous software could divulge to someone information about Intel&#8217;s business, e.g. it could have divulged, or appeared to, information about fab yields in one case and product orders in some other cases.</p>
<p>In the case of testing products, the software structure itself could divulge information about what Intel is testing, how they&#8217;re testing, etc. Maybe that&#8217;s harmless, maybe not. But Intel is a competitive company and has an obligation to its shareholders to protect its interests. Sometimes those interests are served by open source, and sometimes the decision has to be made the other way, hopefully wisely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DeltaStreams 0.1.1 in the works by HOW SHIT WORKS &#187; DeltaStreams 0.1.1 in the &#60;b&#62;works&#60;/b&#62;</title>
		<link>http://mtfulmer.wordpress.com/2007/11/29/deltastreams-011-in-the-works/#comment-914</link>
		<dc:creator>HOW SHIT WORKS &#187; DeltaStreams 0.1.1 in the &#60;b&#62;works&#60;/b&#62;</dc:creator>
		<pubDate>Thu, 29 Nov 2007 22:04:51 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/2007/11/29/deltastreams-011-in-the-works/#comment-914</guid>
		<description>[...] Check This Out! While looking through the blogosphere we stumbled on an interesting post today. Here’s a quick excerpt: I don’t update my blog nearly enough. I released DeltaStreams (with Goran’s approval), nearly a month ago (announcement). Since then, I’ve been working on a few improvements in my (currently copious) spare time. &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Check This Out! While looking through the blogosphere we stumbled on an interesting post today. Here’s a quick excerpt: I don’t update my blog nearly enough. I released DeltaStreams (with Goran’s approval), nearly a month ago (announcement). Since then, I’ve been working on a few improvements in my (currently copious) spare time. &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How not to port software by How not to port software, part 2 &#171; And I thank God for&#8230;</title>
		<link>http://mtfulmer.wordpress.com/2007/02/07/how-not-to-port-software/#comment-7</link>
		<dc:creator>How not to port software, part 2 &#171; And I thank God for&#8230;</dc:creator>
		<pubDate>Fri, 23 Feb 2007 03:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/2007/02/07/how-not-to-port-software/#comment-7</guid>
		<description>[...] software, part&#160;2 23 February 2007 Posted by Matthew Fulmer in Uncategorized. trackback  In my previous post, I told about my experience trying to port a windows-only C++ program first to the cross-platform [...]</description>
		<content:encoded><![CDATA[<p>[...] software, part&nbsp;2 23 February 2007 Posted by Matthew Fulmer in Uncategorized. trackback  In my previous post, I told about my experience trying to port a windows-only C++ program first to the cross-platform [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How not to port software by nicolas cellier</title>
		<link>http://mtfulmer.wordpress.com/2007/02/07/how-not-to-port-software/#comment-6</link>
		<dc:creator>nicolas cellier</dc:creator>
		<pubDate>Tue, 20 Feb 2007 11:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/2007/02/07/how-not-to-port-software/#comment-6</guid>
		<description>Hello Matthew
I am very sorry your Smallapack experience failed.
Sorry but not amazed.
What you should learn before using a package:
- mind the tags: Smallapack is tagged bleding edge
- use provided SUnit test cases: you would see some are failing

In fact, Smallapack is usable only in VW by now (and i did not say bugfree, test cases need to be completed).

If you persist in using such a package, my advices would be:
- do not hesitate to ask support (it does not cost to ask)
- please share your critics, bugfixes, improvements
I think collaborating is the fastest way to improve such a general purpose package.

Cheers</description>
		<content:encoded><![CDATA[<p>Hello Matthew<br />
I am very sorry your Smallapack experience failed.<br />
Sorry but not amazed.<br />
What you should learn before using a package:<br />
- mind the tags: Smallapack is tagged bleding edge<br />
- use provided SUnit test cases: you would see some are failing</p>
<p>In fact, Smallapack is usable only in VW by now (and i did not say bugfree, test cases need to be completed).</p>
<p>If you persist in using such a package, my advices would be:<br />
- do not hesitate to ask support (it does not cost to ask)<br />
- please share your critics, bugfixes, improvements<br />
I think collaborating is the fastest way to improve such a general purpose package.</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How not to port software by nicolas cellier</title>
		<link>http://mtfulmer.wordpress.com/2007/02/07/how-not-to-port-software/#comment-5</link>
		<dc:creator>nicolas cellier</dc:creator>
		<pubDate>Tue, 20 Feb 2007 09:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://mtfulmer.wordpress.com/2007/02/07/how-not-to-port-software/#comment-5</guid>
		<description>Hello Matthew,
very sorry Smallapack did not fit, but this is not amazing.
what you should learn before using a package:
- mind the tags: Squeak Smallapack is tagged bleding edge
- run the SUnit test cases: you should have seen they do not work
Only the VW version is usable (did not say bugfree).

If you persist in using Squeak version, correct some bugs or do some improvements, please share your work. Collaborating is the fastest way to obtain something working. Maybe you have done some good work that will be lost now.

And also, do not hesitate to ask for support, it costs nothing to ask...

Cheers</description>
		<content:encoded><![CDATA[<p>Hello Matthew,<br />
very sorry Smallapack did not fit, but this is not amazing.<br />
what you should learn before using a package:<br />
- mind the tags: Squeak Smallapack is tagged bleding edge<br />
- run the SUnit test cases: you should have seen they do not work<br />
Only the VW version is usable (did not say bugfree).</p>
<p>If you persist in using Squeak version, correct some bugs or do some improvements, please share your work. Collaborating is the fastest way to obtain something working. Maybe you have done some good work that will be lost now.</p>
<p>And also, do not hesitate to ask for support, it costs nothing to ask&#8230;</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
</channel>
</rss>
