<?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/"
	>
<channel>
	<title>Comments on: Software: Work or Labor?</title>
	<atom:link href="http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/feed/" rel="self" type="application/rss+xml" />
	<link>http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/</link>
	<description></description>
	<pubDate>Thu, 09 Feb 2012 10:41:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: grex</title>
		<link>http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/comment-page-1/#comment-1470</link>
		<dc:creator>grex</dc:creator>
		<pubDate>Sat, 21 May 2005 15:14:28 +0000</pubDate>
		<guid isPermaLink="false">http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/#comment-1470</guid>
		<description>thanks for fixing what I messed up, Niklas.

I agree with the idea the libre software should be theoretically less prone to aging. We have done some empirical work on this for some libre software projects, but haven't data to compare it against proprietary software.

On the other hand, I want to point out that there is not that much difference for working on a libre software project or on a proprietary one for the ones who actually work on them. For both of them, and with current laws being the copyright holders means to own the software in the same way.

My point is that the big difference is for the ones who receive the software not for the ones who create it, so that's why I don't see the labor vs. work argument being of importance in this area.</description>
		<content:encoded><![CDATA[<p>thanks for fixing what I messed up, Niklas.</p>
<p>I agree with the idea the libre software should be theoretically less prone to aging. We have done some empirical work on this for some libre software projects, but haven&#8217;t data to compare it against proprietary software.</p>
<p>On the other hand, I want to point out that there is not that much difference for working on a libre software project or on a proprietary one for the ones who actually work on them. For both of them, and with current laws being the copyright holders means to own the software in the same way.</p>
<p>My point is that the big difference is for the ones who receive the software not for the ones who create it, so that&#8217;s why I don&#8217;t see the labor vs. work argument being of importance in this area.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niklas Vainio</title>
		<link>http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/comment-page-1/#comment-1469</link>
		<dc:creator>Niklas Vainio</dc:creator>
		<pubDate>Sat, 21 May 2005 10:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/#comment-1469</guid>
		<description>grex, thanks for your cents and links. The paper looks interesting. I also fixed your markup.

I share most of your criticism. Although I agree with many Marxist ideas, I'm not so sure about the alienation theory. On the other hand, there is a difference between work done for a proprietary software company and the work done for the joy of hacking. The latter may lead to active life, politics etc. And although particular versions of KDE become less useful, the KDE software as an idea (or codebase or community) is less prone to aging because it is maintained by the community. This can happen with proprietary software as well, but it will stop on the day the company goes bankcrupt.</description>
		<content:encoded><![CDATA[<p>grex, thanks for your cents and links. The paper looks interesting. I also fixed your markup.</p>
<p>I share most of your criticism. Although I agree with many Marxist ideas, I&#8217;m not so sure about the alienation theory. On the other hand, there is a difference between work done for a proprietary software company and the work done for the joy of hacking. The latter may lead to active life, politics etc. And although particular versions of KDE become less useful, the KDE software as an idea (or codebase or community) is less prone to aging because it is maintained by the community. This can happen with proprietary software as well, but it will stop on the day the company goes bankcrupt.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grex</title>
		<link>http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/comment-page-1/#comment-1467</link>
		<dc:creator>grex</dc:creator>
		<pubDate>Fri, 20 May 2005 14:52:21 +0000</pubDate>
		<guid isPermaLink="false">http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/#comment-1467</guid>
		<description>oh, sorry, got my HTML wrong in the previous post. I'm really sorry.</description>
		<content:encoded><![CDATA[<p>oh, sorry, got my HTML wrong in the previous post. I&#8217;m really sorry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grex</title>
		<link>http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/comment-page-1/#comment-1466</link>
		<dc:creator>grex</dc:creator>
		<pubDate>Fri, 20 May 2005 14:51:01 +0000</pubDate>
		<guid isPermaLink="false">http://hiisi.fi/blog/post/2005/05/19/software-work-or-labor/#comment-1466</guid>
		<description>Let me a little bit critic with this point of view. Software is "something that lasts", but it is known for many years now that software also ages, a concept coined by David Parnas in his &lt;a href="http://portal.acm.org/citation.cfm?id=257788" rel="nofollow"&gt;Software Aging&lt;/a&gt; paper around ten years ago. This has been also the matter of study for many researchers, among others Lehman and his findings known as the &lt;i&gt;laws&lt;/i&gt; of software evolution (see &lt;a href="http://www.manageability.org/blog/stuff/the-8-laws-of-software-evolution/view" rel="nofollow"&gt;here&lt;/a&gt;) which applies to E-type software which is almost all software. The first law one (known as 'Continuing Change') says that a system must be continually adapted else they become progressively less satisfactory in use. So, even if software is mathematically perfect, but it becomes in time less and less useful (that's why yo probably use one of the most recent versions of GNOME or KDE and not the ones from 1998 for instance). If you consider this, I don't know if we should put software as labour or as work. My two cents ;-)</description>
		<content:encoded><![CDATA[<p>Let me a little bit critic with this point of view. Software is &#8220;something that lasts&#8221;, but it is known for many years now that software also ages, a concept coined by David Parnas in his <a href="http://portal.acm.org/citation.cfm?id=257788" rel="nofollow">Software Aging</a> paper around ten years ago. This has been also the matter of study for many researchers, among others Lehman and his findings known as the <i>laws</i> of software evolution (see <a href="http://www.manageability.org/blog/stuff/the-8-laws-of-software-evolution/view" rel="nofollow">here</a>) which applies to E-type software which is almost all software. The first law one (known as &#8216;Continuing Change&#8217;) says that a system must be continually adapted else they become progressively less satisfactory in use. So, even if software is mathematically perfect, but it becomes in time less and less useful (that&#8217;s why yo probably use one of the most recent versions of GNOME or KDE and not the ones from 1998 for instance). If you consider this, I don&#8217;t know if we should put software as labour or as work. My two cents ;-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

