<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The Invisible Closed Source Overhead &#8211; 1</title>
	<atom:link href="http://brendanscott.wordpress.com/2008/06/20/the-invisible-closed-source-overhead-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://brendanscott.wordpress.com/2008/06/20/the-invisible-closed-source-overhead-1/</link>
	<description>Comments on Life and Law, Free Software, Open Source and Intellectual Monopolies</description>
	<lastBuildDate>Mon, 14 Dec 2009 13:09:19 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Invisible Closed Source Overhead - 3 &#171; Brendan Scott&#8217;s Weblog</title>
		<link>http://brendanscott.wordpress.com/2008/06/20/the-invisible-closed-source-overhead-1/#comment-1145</link>
		<dc:creator>The Invisible Closed Source Overhead - 3 &#171; Brendan Scott&#8217;s Weblog</dc:creator>
		<pubDate>Tue, 13 Jan 2009 12:46:43 +0000</pubDate>
		<guid isPermaLink="false">http://brendanscott.wordpress.com/?p=69#comment-1145</guid>
		<description>[...] The Invisible Closed Source Overhead - 1 [...]</description>
		<content:encoded><![CDATA[<p>[...] The Invisible Closed Source Overhead &#8211; 1 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlpahG</title>
		<link>http://brendanscott.wordpress.com/2008/06/20/the-invisible-closed-source-overhead-1/#comment-338</link>
		<dc:creator>AlpahG</dc:creator>
		<pubDate>Wed, 25 Jun 2008 11:32:36 +0000</pubDate>
		<guid isPermaLink="false">http://brendanscott.wordpress.com/?p=69#comment-338</guid>
		<description>Any implementation which is designed to be sold on a per unit basis (regardless of the unit - eg copy, seat, site, user etc) means it must be designed to maximise sales of that unit. Here the 80-20 rule comes into play, with the vendor coding features to attract a large chunk of the market for the lowest cost. That is, in order to maximise profits a closed source vendor must aim for a product which is “good enough for most”.

Again you are dead right here as Novell and Red Hat both sell a subscription service with their product in the Open Source space, sold per desktop, per user etc. You cannot buy the commercial releases of their solutions without payment. Microsoft also have licensing schemes but like many they offer choice to minimise costs with does seem to negate your maximise sales discussion. For example a hospital has 15000 staff and 5000 devices who work in three shifts, In this scenario you pay per device not per staff member. An alternate is an IT company where each person mmay have a desktop, laptop and multiple devices, for example Microsoft where there are 55000 employees and &gt; 150,000 devices. In this case you license by user. You are able to mix and match also with the different schemes.

You could say it is vendor lockin, you may be right but every organisation must do its due diligence when selecting its applications. The applications which meet its business needs will have choices for the platform they run on. The company must invest where it sees its best returns. They must do a cost analysis over the life of the application what it will cost to license, administer, support etc etc. If they do not then they are stupid and deserve to be plundered. No matter what they choose there is a cost for all choices, they just need to make wise business and commercial decisions that keep the business in front of others.</description>
		<content:encoded><![CDATA[<p>Any implementation which is designed to be sold on a per unit basis (regardless of the unit &#8211; eg copy, seat, site, user etc) means it must be designed to maximise sales of that unit. Here the 80-20 rule comes into play, with the vendor coding features to attract a large chunk of the market for the lowest cost. That is, in order to maximise profits a closed source vendor must aim for a product which is “good enough for most”.</p>
<p>Again you are dead right here as Novell and Red Hat both sell a subscription service with their product in the Open Source space, sold per desktop, per user etc. You cannot buy the commercial releases of their solutions without payment. Microsoft also have licensing schemes but like many they offer choice to minimise costs with does seem to negate your maximise sales discussion. For example a hospital has 15000 staff and 5000 devices who work in three shifts, In this scenario you pay per device not per staff member. An alternate is an IT company where each person mmay have a desktop, laptop and multiple devices, for example Microsoft where there are 55000 employees and &gt; 150,000 devices. In this case you license by user. You are able to mix and match also with the different schemes.</p>
<p>You could say it is vendor lockin, you may be right but every organisation must do its due diligence when selecting its applications. The applications which meet its business needs will have choices for the platform they run on. The company must invest where it sees its best returns. They must do a cost analysis over the life of the application what it will cost to license, administer, support etc etc. If they do not then they are stupid and deserve to be plundered. No matter what they choose there is a cost for all choices, they just need to make wise business and commercial decisions that keep the business in front of others.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AlpahG</title>
		<link>http://brendanscott.wordpress.com/2008/06/20/the-invisible-closed-source-overhead-1/#comment-337</link>
		<dc:creator>AlpahG</dc:creator>
		<pubDate>Wed, 25 Jun 2008 11:22:56 +0000</pubDate>
		<guid isPermaLink="false">http://brendanscott.wordpress.com/?p=69#comment-337</guid>
		<description>&quot;Indeed, the gap between their requirements and the capability of close source solutions is so great that Universities have banded together to create their own (open source) accounting software - at substantial expense. Ordinarily you would expect that Universities would have enough market power to get additional functionality into closed source solutions - but they don’t. Remarkably, the US University sector is not important enough to influence the direction of closed source software vendors on features of their accounting software.&quot;

Hey I love this, as it finally recognises no matter whether open or closed source an application especially of significant effort costs significant money. It is not free to develop and maintain and the largest cost is peoples time. The difference is what happens to the applciation at the first hurdle (first version). Does the person or group need to recouperate its investment, do they want to own the IP, do they want to share it. If they work for &quot;the man&quot; then it is likely they receive compensation for their effort but the rights belong to &quot;the man&quot;.

Interestingly it all depends when it comes to closed source applciations and customer demand and directions. I can tell you Telstra was the largest MS Mail user in the southern hemisphere and they had significant input into the first version of Exchange and have done so for every release since. Microsoft absolutely takes notice when they request new features and changes etc during beta projects. Of course there is an outcome for Microsoft in that they can then sell the product to its customers.</description>
		<content:encoded><![CDATA[<p>&#8220;Indeed, the gap between their requirements and the capability of close source solutions is so great that Universities have banded together to create their own (open source) accounting software &#8211; at substantial expense. Ordinarily you would expect that Universities would have enough market power to get additional functionality into closed source solutions &#8211; but they don’t. Remarkably, the US University sector is not important enough to influence the direction of closed source software vendors on features of their accounting software.&#8221;</p>
<p>Hey I love this, as it finally recognises no matter whether open or closed source an application especially of significant effort costs significant money. It is not free to develop and maintain and the largest cost is peoples time. The difference is what happens to the applciation at the first hurdle (first version). Does the person or group need to recouperate its investment, do they want to own the IP, do they want to share it. If they work for &#8220;the man&#8221; then it is likely they receive compensation for their effort but the rights belong to &#8220;the man&#8221;.</p>
<p>Interestingly it all depends when it comes to closed source applciations and customer demand and directions. I can tell you Telstra was the largest MS Mail user in the southern hemisphere and they had significant input into the first version of Exchange and have done so for every release since. Microsoft absolutely takes notice when they request new features and changes etc during beta projects. Of course there is an outcome for Microsoft in that they can then sell the product to its customers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clive</title>
		<link>http://brendanscott.wordpress.com/2008/06/20/the-invisible-closed-source-overhead-1/#comment-306</link>
		<dc:creator>Clive</dc:creator>
		<pubDate>Tue, 24 Jun 2008 06:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://brendanscott.wordpress.com/?p=69#comment-306</guid>
		<description>Since 20% is a large number you might be better referring to the 80% group and the 20% group by &quot;80%&quot; and &quot;20%&quot; rather than using the word &quot;few&quot; which implies that there aren&#039;t many in the group.</description>
		<content:encoded><![CDATA[<p>Since 20% is a large number you might be better referring to the 80% group and the 20% group by &#8220;80%&#8221; and &#8220;20%&#8221; rather than using the word &#8220;few&#8221; which implies that there aren&#8217;t many in the group.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pia</title>
		<link>http://brendanscott.wordpress.com/2008/06/20/the-invisible-closed-source-overhead-1/#comment-298</link>
		<dc:creator>Pia</dc:creator>
		<pubDate>Sat, 21 Jun 2008 04:18:50 +0000</pubDate>
		<guid isPermaLink="false">http://brendanscott.wordpress.com/?p=69#comment-298</guid>
		<description>Thanks Brendan, that was really useful!</description>
		<content:encoded><![CDATA[<p>Thanks Brendan, that was really useful!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
