<?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: To Limit, or Not To Limit</title>
	<atom:link href="http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=to-limit-or-not-to-limit</link>
	<description>Patrick McKenzie (patio11) blogs on software development, marketing, and general business topics</description>
	<lastBuildDate>Sat, 11 Feb 2012 04:17:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Should You Offer Free Trials &#124; Software Marketing Secrets</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-279</link>
		<dc:creator>Should You Offer Free Trials &#124; Software Marketing Secrets</dc:creator>
		<pubDate>Mon, 26 Sep 2011 07:58:24 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-279</guid>
		<description>[...] McKenzie reports on an A/B test of nagware vs feature-limited versions of the same software, showing the feature limited version had a 5 times higher conversion [...]</description>
		<content:encoded><![CDATA[<p>[...] McKenzie reports on an A/B test of nagware vs feature-limited versions of the same software, showing the feature limited version had a 5 times higher conversion [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What type of free trial should I offer for my software? &#171; Successful Software</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-278</link>
		<dc:creator>What type of free trial should I offer for my software? &#171; Successful Software</dc:creator>
		<pubDate>Mon, 19 Sep 2011 16:00:26 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-278</guid>
		<description>[...] McKenzie reports on an A/B test of nagware vs feature-limited versions of the same software, showing the feature limited version had a 5 times higher conversion [...]</description>
		<content:encoded><![CDATA[<p>[...] McKenzie reports on an A/B test of nagware vs feature-limited versions of the same software, showing the feature limited version had a 5 times higher conversion [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nursing credit cards</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-277</link>
		<dc:creator>nursing credit cards</dc:creator>
		<pubDate>Fri, 01 Aug 2008 20:42:31 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-277</guid>
		<description>eajtzs mecd</description>
		<content:encoded><![CDATA[<p>eajtzs mecd</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geoff Dodd</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-276</link>
		<dc:creator>Geoff Dodd</dc:creator>
		<pubDate>Sat, 17 Feb 2007 07:23:03 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-276</guid>
		<description>To Limit, or Not?  Nice article which proves behavioral psychology correct! People act according to the contingencies of reward. If x then y.  If they can get FULL FEATURED software for nix then they&#039;ll pay nought. Zilch donated or 0.38 cents as you say. So I think you&#039;re quite right to limit by features until money is forthcoming. After all - you&#039;re in the software Business! Not gifting.

Additionally, I can say I&#039;ve found open source software to be disappointing - unless you consider Mozilla Firefox to be open source. It&#039;s free and fine ware.

Geoff Dodd
Australia</description>
		<content:encoded><![CDATA[<p>To Limit, or Not?  Nice article which proves behavioral psychology correct! People act according to the contingencies of reward. If x then y.  If they can get FULL FEATURED software for nix then they&#8217;ll pay nought. Zilch donated or 0.38 cents as you say. So I think you&#8217;re quite right to limit by features until money is forthcoming. After all &#8211; you&#8217;re in the software Business! Not gifting.</p>
<p>Additionally, I can say I&#8217;ve found open source software to be disappointing &#8211; unless you consider Mozilla Firefox to be open source. It&#8217;s free and fine ware.</p>
<p>Geoff Dodd<br />
Australia</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heherson Tan</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-275</link>
		<dc:creator>Heherson Tan</dc:creator>
		<pubDate>Tue, 24 Oct 2006 08:59:00 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-275</guid>
		<description>Hi Franco, Mercury Merliin and other OSS guys,

I am just curious, how are you guys making a living? Are you paid programmers of OSS companies? If you are, I bet these companies have business model themselves. They just have different business models, like selling support instead of selling the software itself, or selling the hardware the OSS runs on.

Truth is, software development is not possible with cash / financing. People and businesses that develop software must find a way to finance their development. If you are a volunteer programmer, you either must have a day job or ask people for grant or donations. Either way, your &#039;business model&#039; goes like these &quot;I&#039;ll work on these OSS project at night / weekend, but I&#039;ll work for AAA as an employee so I can pay the bills, etc&quot;.

Software Developers who sell their stuff most likely have something like these &quot;I&#039;ll develop these software, then users can use them for a fee.&quot;

Shareware Business has little difference from traditional brick and mortar businesses. You develop a product, you sell it. To compute how much you want to sell your product: PRICE = (OVERHEAD + PROFIT) / NUMBER_OF_ITEMS + MARGINAL_COST.

The main difference I think is only the fact that the marginal cost of each product is so low or almost zero. The bulk of the cost is in the overhead (development cost). Implications? Like all businesses with low marginal cost and high overhead cost, you could be very successful or you can fail.

BTW, even if a software still sells for 10 or 20 years or forever with zero development and marketing (how it could be??), you compute the Net Present Value of all the revenue. That means a revenue of $5000 a year for the next 20 years doesn&#039;t earned

Some of these companies are OSS companies, or at least companies admired by OSS community (I should know, I am a part of it):
1.) REDHAT - Sells subscription based support for a distribution of their Linux. Even though REDHAT LINUX is OSS, it is awfully though to get one. In no small part to efforts of REDHAT. See, if you subscribe to their OS support, part of the support contract forbids you to distribute and install the OS on more machines. So much for FREE as in FREEDOM.
2.) Google - Google support OSS by directly by the google code project (sponsoring approved projects and paying its developers) and other indirect means. This is nice. But has anyone of you got their source codes for their of engine? of their clustering architecture?
3.) IBM - IBM helps the community by direct funding of OSS projects and OSDL, releasing its patents for OSS use, etc. Hey, IBM just sued Amazon for one of its patent, and receving $1billion a year for patent licensing. So much for &#039;sharing your intellectual property so other people can use it&#039;.

Point is, these companies are not evil. Like all companies, they must earn money and must protect their competitive advantage. OSS and commercial softwares can coexist. A pragmatic person must choose which model will be more appropriate. There is no problem with that. The problem starts when one starts shoving his model / idealogy down somebody else throat.</description>
		<content:encoded><![CDATA[<p>Hi Franco, Mercury Merliin and other OSS guys,</p>
<p>I am just curious, how are you guys making a living? Are you paid programmers of OSS companies? If you are, I bet these companies have business model themselves. They just have different business models, like selling support instead of selling the software itself, or selling the hardware the OSS runs on.</p>
<p>Truth is, software development is not possible with cash / financing. People and businesses that develop software must find a way to finance their development. If you are a volunteer programmer, you either must have a day job or ask people for grant or donations. Either way, your &#8216;business model&#8217; goes like these &#8220;I&#8217;ll work on these OSS project at night / weekend, but I&#8217;ll work for AAA as an employee so I can pay the bills, etc&#8221;.</p>
<p>Software Developers who sell their stuff most likely have something like these &#8220;I&#8217;ll develop these software, then users can use them for a fee.&#8221;</p>
<p>Shareware Business has little difference from traditional brick and mortar businesses. You develop a product, you sell it. To compute how much you want to sell your product: PRICE = (OVERHEAD + PROFIT) / NUMBER_OF_ITEMS + MARGINAL_COST.</p>
<p>The main difference I think is only the fact that the marginal cost of each product is so low or almost zero. The bulk of the cost is in the overhead (development cost). Implications? Like all businesses with low marginal cost and high overhead cost, you could be very successful or you can fail.</p>
<p>BTW, even if a software still sells for 10 or 20 years or forever with zero development and marketing (how it could be??), you compute the Net Present Value of all the revenue. That means a revenue of $5000 a year for the next 20 years doesn&#8217;t earned</p>
<p>Some of these companies are OSS companies, or at least companies admired by OSS community (I should know, I am a part of it):<br />
1.) REDHAT &#8211; Sells subscription based support for a distribution of their Linux. Even though REDHAT LINUX is OSS, it is awfully though to get one. In no small part to efforts of REDHAT. See, if you subscribe to their OS support, part of the support contract forbids you to distribute and install the OS on more machines. So much for FREE as in FREEDOM.<br />
2.) Google &#8211; Google support OSS by directly by the google code project (sponsoring approved projects and paying its developers) and other indirect means. This is nice. But has anyone of you got their source codes for their of engine? of their clustering architecture?<br />
3.) IBM &#8211; IBM helps the community by direct funding of OSS projects and OSDL, releasing its patents for OSS use, etc. Hey, IBM just sued Amazon for one of its patent, and receving $1billion a year for patent licensing. So much for &#8216;sharing your intellectual property so other people can use it&#8217;.</p>
<p>Point is, these companies are not evil. Like all companies, they must earn money and must protect their competitive advantage. OSS and commercial softwares can coexist. A pragmatic person must choose which model will be more appropriate. There is no problem with that. The problem starts when one starts shoving his model / idealogy down somebody else throat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everything You Need To Know About Registration Systems &#171; MicroISV on a Shoestring</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-274</link>
		<dc:creator>Everything You Need To Know About Registration Systems &#171; MicroISV on a Shoestring</dc:creator>
		<pubDate>Tue, 05 Sep 2006 03:29:53 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-274</guid>
		<description>[...] First, a brief discussion on why you want to protect your software. The only reason you want to protect your software is to enforce the limitations you have put on the trial version. Many people mistakenly come to the table with the assumption that protecting the software will somehow, magically, &#8220;protect my intellectual property&#8221; or something to that effect. This might be theoretically true but you will have an easier time conceptualizing your registration scheme if you think of it as primarily a marketing, rather than technical, measure. Its your salesman that encourages folks to pay you money. [...]</description>
		<content:encoded><![CDATA[<p>[...] First, a brief discussion on why you want to protect your software. The only reason you want to protect your software is to enforce the limitations you have put on the trial version. Many people mistakenly come to the table with the assumption that protecting the software will somehow, magically, &#8220;protect my intellectual property&#8221; or something to that effect. This might be theoretically true but you will have an easier time conceptualizing your registration scheme if you think of it as primarily a marketing, rather than technical, measure. Its your salesman that encourages folks to pay you money. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thank God for the French!</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-273</link>
		<dc:creator>Thank God for the French!</dc:creator>
		<pubDate>Sat, 02 Sep 2006 02:56:03 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-273</guid>
		<description>A. The open source quality guy. Good measurements yah. It isn&#039;t like you&#039;re talking out of your ass there. I doubt you even know what you mean by when you say quality. Regardless, commercial and open source software are not that different and how they&#039;re developed and who develops them are not different. Perhaps you are getting the software at a different time.

B. You should be ashamed of yourself for making shareware. Denying all other users the freedom to use your software freely (as in freedom) is sinful and plain wrong. Regardless your software is simple and trivial, it isn&#039;t worth the money and I feel sorry for anyone who paid for your product and didn&#039;t get the source code.

So continue to talk out of your ass, it isn&#039;t like slashdot isn&#039;t used to it.</description>
		<content:encoded><![CDATA[<p>A. The open source quality guy. Good measurements yah. It isn&#8217;t like you&#8217;re talking out of your ass there. I doubt you even know what you mean by when you say quality. Regardless, commercial and open source software are not that different and how they&#8217;re developed and who develops them are not different. Perhaps you are getting the software at a different time.</p>
<p>B. You should be ashamed of yourself for making shareware. Denying all other users the freedom to use your software freely (as in freedom) is sinful and plain wrong. Regardless your software is simple and trivial, it isn&#8217;t worth the money and I feel sorry for anyone who paid for your product and didn&#8217;t get the source code.</p>
<p>So continue to talk out of your ass, it isn&#8217;t like slashdot isn&#8217;t used to it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-272</link>
		<dc:creator>Jacob</dc:creator>
		<pubDate>Fri, 01 Sep 2006 20:18:10 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-272</guid>
		<description>Regarding Franko&#039;s post:

&gt;
Yeah, that&#039;s the problem alright. It&#039;s them darn programmers expecting to make a living doing something that&#039;s so simple that most of the population can&#039;t do it. You&#039;ve been watching too many RoR demos.

&gt;
This is also the proper way for plumbers, artists, farmers, and mechanics to be paid. There is one little snag though. You may not be old enough to remember, but they tried this a while back and the result was people waiting in line for days for a loaf of bread and some milk. You&#039;ve obviously thought of something they didn&#039;t though, so please, do share your wisdom. Meanwhile, i&#039;ll just have to live with the (obviously inferior) free market approach, where value-provider and value-receiver have to work out the details of how and how much is paid for a product without the government to act as a custodian. (There are so many problems with the model that you suggest that a whole book could be written on the subject, but I digress)

&gt;
90% or more of open source software is incredibly hideous, especially in the usability and documentation departments. There are good reasons for that, some of which Patrick covers here:

http://microisvjournal.wordpress.com/2006/08/23/open-source-vs-uisvs-some-myths-that-need-to-die/

Regarding Mercury&#039;s post:

You my friend are the one who missed the point. Any programmer unable to come up with &quot;free/libre != free/gratis&quot; on their own has been living in a cave for at least the last decade. Here is a couple more for you from my original post:

Freeloaders != Open Source
Freeloaders == those wanting to benefit from everyone else&#039;s work without giving anything in return

This is, in fact, what you want. You just won&#039;t come out and say it. The real reason you, Franko, and many others want so badly for ALL software to be open sourced is so that you can use any program you please, without having to pay for it, and not feel guilty about pirating it.

It&#039;s a sense of entitlement expressed as a complete disregard for the countless hours of preparation, money, and work that go into creating, promoting, distributing, supporting, and maintaining a product. All of this effort is rationalized away to naught with a simplistic argument about how the cost of duplication (which is not zero, even for a bits and bytes) should be the only recoverable cost of doing business. And heaven forbid that anyone should be able to make a profit from selling the goods you consume. (This is like arguing that a car dealership should only be able to charge for the cost of materials on the cars they sell)

Creating anything of value (physical or digital) and putting it to market requires an investment of time (for preparation and production), money, or more often, both. Just as with an investment in the stock market, an investment in creating a program involves risk - sometimes LOTS of risk. The only way to get people to take these risks is if there is sufficient incentive to do so. Usually the incentive in this case is the possibility of higher returns than say, working for McDonalds.

Your assertion that 2000 hours invested in a product is worth some arbitrary value approximately equal to one year’s salary shows a complete lack of understanding not only of the effort involved in running your own business, but also of basic free market economics. If you&#039;re punching a timecard every day and getting a regular paycheck, you are effectively accepting a lower return (your salary) in order to reduce your exposure to risk. If you&#039;re a consultant, there&#039;s a possibility that you’ll have many more gaps between paying jobs (risk), so consultants get paid more. If I decide to create a program to sell, the risk may be orders of magnitude higher. Let&#039;s say I have to invest 2000 hours (1 yr, full time) plus operating expenses for that year (rent, food, etc), and I have no monthly paycheck coming in and no guarantee of any return at all. No sane person would make that kind of investment, with that much risk, without the potential for higher returns than those same 2000 hours invested in a full time job with an almost. This is not freeloading; it’s supply vs. demand and risk vs. return - the same principles that drive everything from produce prices to stock prices to interest rates on car loans.

This also helps explain why open source software is usually of much poorer quality than equivalent commercial software. Creating high quality software, and everything that goes with it, can take a huge amount of effort, even for a fairly simple program. It&#039;s the rare open source project where there is sufficient incentive for contributors to invest this level of effort. The few exceptions to this rule are almost always that way because they are used as a loss-leader for something else.

Paul Grahm has a very good essay that, while not really addressing commercial vs. open source, certainly explains why the extremes you suggest would kill or at least severely dampen innovation in software or any other industry:

http://www.paulgraham.com/wealth.html

The section titled &quot;The Pie Fallacy&quot; is very relevant to your misconceptions about commercial software and freeloading.</description>
		<content:encoded><![CDATA[<p>Regarding Franko&#8217;s post:</p>
<p>&gt;<br />
Yeah, that&#8217;s the problem alright. It&#8217;s them darn programmers expecting to make a living doing something that&#8217;s so simple that most of the population can&#8217;t do it. You&#8217;ve been watching too many RoR demos.</p>
<p>&gt;<br />
This is also the proper way for plumbers, artists, farmers, and mechanics to be paid. There is one little snag though. You may not be old enough to remember, but they tried this a while back and the result was people waiting in line for days for a loaf of bread and some milk. You&#8217;ve obviously thought of something they didn&#8217;t though, so please, do share your wisdom. Meanwhile, i&#8217;ll just have to live with the (obviously inferior) free market approach, where value-provider and value-receiver have to work out the details of how and how much is paid for a product without the government to act as a custodian. (There are so many problems with the model that you suggest that a whole book could be written on the subject, but I digress)</p>
<p>&gt;<br />
90% or more of open source software is incredibly hideous, especially in the usability and documentation departments. There are good reasons for that, some of which Patrick covers here:</p>
<p><a href="http://microisvjournal.wordpress.com/2006/08/23/open-source-vs-uisvs-some-myths-that-need-to-die/" rel="nofollow">http://microisvjournal.wordpress.com/2006/08/23/open-source-vs-uisvs-some-myths-that-need-to-die/</a></p>
<p>Regarding Mercury&#8217;s post:</p>
<p>You my friend are the one who missed the point. Any programmer unable to come up with &#8220;free/libre != free/gratis&#8221; on their own has been living in a cave for at least the last decade. Here is a couple more for you from my original post:</p>
<p>Freeloaders != Open Source<br />
Freeloaders == those wanting to benefit from everyone else&#8217;s work without giving anything in return</p>
<p>This is, in fact, what you want. You just won&#8217;t come out and say it. The real reason you, Franko, and many others want so badly for ALL software to be open sourced is so that you can use any program you please, without having to pay for it, and not feel guilty about pirating it.</p>
<p>It&#8217;s a sense of entitlement expressed as a complete disregard for the countless hours of preparation, money, and work that go into creating, promoting, distributing, supporting, and maintaining a product. All of this effort is rationalized away to naught with a simplistic argument about how the cost of duplication (which is not zero, even for a bits and bytes) should be the only recoverable cost of doing business. And heaven forbid that anyone should be able to make a profit from selling the goods you consume. (This is like arguing that a car dealership should only be able to charge for the cost of materials on the cars they sell)</p>
<p>Creating anything of value (physical or digital) and putting it to market requires an investment of time (for preparation and production), money, or more often, both. Just as with an investment in the stock market, an investment in creating a program involves risk &#8211; sometimes LOTS of risk. The only way to get people to take these risks is if there is sufficient incentive to do so. Usually the incentive in this case is the possibility of higher returns than say, working for McDonalds.</p>
<p>Your assertion that 2000 hours invested in a product is worth some arbitrary value approximately equal to one year’s salary shows a complete lack of understanding not only of the effort involved in running your own business, but also of basic free market economics. If you&#8217;re punching a timecard every day and getting a regular paycheck, you are effectively accepting a lower return (your salary) in order to reduce your exposure to risk. If you&#8217;re a consultant, there&#8217;s a possibility that you’ll have many more gaps between paying jobs (risk), so consultants get paid more. If I decide to create a program to sell, the risk may be orders of magnitude higher. Let&#8217;s say I have to invest 2000 hours (1 yr, full time) plus operating expenses for that year (rent, food, etc), and I have no monthly paycheck coming in and no guarantee of any return at all. No sane person would make that kind of investment, with that much risk, without the potential for higher returns than those same 2000 hours invested in a full time job with an almost. This is not freeloading; it’s supply vs. demand and risk vs. return &#8211; the same principles that drive everything from produce prices to stock prices to interest rates on car loans.</p>
<p>This also helps explain why open source software is usually of much poorer quality than equivalent commercial software. Creating high quality software, and everything that goes with it, can take a huge amount of effort, even for a fairly simple program. It&#8217;s the rare open source project where there is sufficient incentive for contributors to invest this level of effort. The few exceptions to this rule are almost always that way because they are used as a loss-leader for something else.</p>
<p>Paul Grahm has a very good essay that, while not really addressing commercial vs. open source, certainly explains why the extremes you suggest would kill or at least severely dampen innovation in software or any other industry:</p>
<p><a href="http://www.paulgraham.com/wealth.html" rel="nofollow">http://www.paulgraham.com/wealth.html</a></p>
<p>The section titled &#8220;The Pie Fallacy&#8221; is very relevant to your misconceptions about commercial software and freeloading.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mercury Merlin</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-271</link>
		<dc:creator>Mercury Merlin</dc:creator>
		<pubDate>Mon, 28 Aug 2006 21:53:57 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-271</guid>
		<description>What&#039;s happened is that a few things have changed, and in a relatively recent timescales. Those winds of change have been blowing for a few decades now, and plenty strong in the last few years.

1) It is now the case that once reduced to digital form, pretty much anything can be distributed everywhere at effectively zero marginal cost. This did not used to be true, and it was very much less true the further back you go. All indications are it is becoming increasingly true as time passes.

2) Copyright has been retrospectively extended so that it&#039;s now effectively perpetual, and digital restrictions are being imposed to enforce it. If this were not the case, if there were not DRM and if copyright expired in a reasonable time (say 7 years, given the fast-moving reality of development today), then I would take some of the arguments favouring copyright and ownership thereof more seriously than I do at present.

Point (1), however, means that to all intents and purposes an idea is no longer distinguishable from the expression of that idea in some fixed, recordable, copyable,  and distributable form (with or without modification). That didn&#039;t used to be the case, not in the same way.

Here&#039;s a free clue: you can&#039;t own an idea. The moment you communicate it, you lose control of it. That&#039;s what&#039;s happening to software, and to other media as well.

The question is not how you prevent that, which is the intention of the digital restriction mentioned (2) (can you stop the tide, King Canute?), the question is what business models are going to work in this new environment.

Free/libre software is one model that seems to work; paid-for custom software as it already exists seems unaffected; grant-based basic research might be another, and there may be more. Proprietary, closed development, however, doesn&#039;t seem to be coping in this environment.

As for the canonical dragon story, I don&#039;t know so much about dragons but you could say that epic fantasy as we know it took off from the roots laid by William Morris in the 19th century with the Wood Beyond the World and The Well at the World&#039;s End; Tolkien and later exist in the shadow of and draw on Morris&#039;s ground-breaking work.

Interestingly, Canonical is the name chosen for Shuttleworth&#039;s company which is spearheading a renaissance of open-source software for Everyman; it is not for no reason that this is so.</description>
		<content:encoded><![CDATA[<p>What&#8217;s happened is that a few things have changed, and in a relatively recent timescales. Those winds of change have been blowing for a few decades now, and plenty strong in the last few years.</p>
<p>1) It is now the case that once reduced to digital form, pretty much anything can be distributed everywhere at effectively zero marginal cost. This did not used to be true, and it was very much less true the further back you go. All indications are it is becoming increasingly true as time passes.</p>
<p>2) Copyright has been retrospectively extended so that it&#8217;s now effectively perpetual, and digital restrictions are being imposed to enforce it. If this were not the case, if there were not DRM and if copyright expired in a reasonable time (say 7 years, given the fast-moving reality of development today), then I would take some of the arguments favouring copyright and ownership thereof more seriously than I do at present.</p>
<p>Point (1), however, means that to all intents and purposes an idea is no longer distinguishable from the expression of that idea in some fixed, recordable, copyable,  and distributable form (with or without modification). That didn&#8217;t used to be the case, not in the same way.</p>
<p>Here&#8217;s a free clue: you can&#8217;t own an idea. The moment you communicate it, you lose control of it. That&#8217;s what&#8217;s happening to software, and to other media as well.</p>
<p>The question is not how you prevent that, which is the intention of the digital restriction mentioned (2) (can you stop the tide, King Canute?), the question is what business models are going to work in this new environment.</p>
<p>Free/libre software is one model that seems to work; paid-for custom software as it already exists seems unaffected; grant-based basic research might be another, and there may be more. Proprietary, closed development, however, doesn&#8217;t seem to be coping in this environment.</p>
<p>As for the canonical dragon story, I don&#8217;t know so much about dragons but you could say that epic fantasy as we know it took off from the roots laid by William Morris in the 19th century with the Wood Beyond the World and The Well at the World&#8217;s End; Tolkien and later exist in the shadow of and draw on Morris&#8217;s ground-breaking work.</p>
<p>Interestingly, Canonical is the name chosen for Shuttleworth&#8217;s company which is spearheading a renaissance of open-source software for Everyman; it is not for no reason that this is so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patrick</title>
		<link>http://www.kalzumeus.com/2006/08/16/to-limit-or-not-to-limit/#comment-270</link>
		<dc:creator>Patrick</dc:creator>
		<pubDate>Sun, 27 Aug 2006 06:36:13 +0000</pubDate>
		<guid isPermaLink="false">https://microisvjournal.wordpress.com/2006/08/16/to-limit-or-not-to-limit/#comment-270</guid>
		<description>That makes about as much sense as saying that free distribution of eBooks on the Internet will kill writing forever, because all one person has to do is write the Canonical Dragon Story (CDS) and there will be, forevermore, no need to pay fantasy authors for dragon stories.  It completely ignores that different readers have different dragon-story needs, that one reader&#039;s CDS is another&#039;s terrible waste of paper, and that despite the fact there are millions of dragon stories already printed each additional one gives at least some value to someone.

Incidentally: can I get a download link to the time synchronizer that completely and for all time solves time synchronization problems for all users?

&gt;&gt;
But the need for even worrying about that issue of how to pay programmers is already past, as virtually all software anybody would need already exists and is open source.
&gt;&gt;

And it all runs in 640 kb of ram, too!</description>
		<content:encoded><![CDATA[<p>That makes about as much sense as saying that free distribution of eBooks on the Internet will kill writing forever, because all one person has to do is write the Canonical Dragon Story (CDS) and there will be, forevermore, no need to pay fantasy authors for dragon stories.  It completely ignores that different readers have different dragon-story needs, that one reader&#8217;s CDS is another&#8217;s terrible waste of paper, and that despite the fact there are millions of dragon stories already printed each additional one gives at least some value to someone.</p>
<p>Incidentally: can I get a download link to the time synchronizer that completely and for all time solves time synchronization problems for all users?</p>
<p>&gt;&gt;<br />
But the need for even worrying about that issue of how to pay programmers is already past, as virtually all software anybody would need already exists and is open source.<br />
&gt;&gt;</p>
<p>And it all runs in 640 kb of ram, too!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

