Ted Leung on the air: Open Source, Java, Python, and ...
Robert Love points to r0ml's articl on ONLamp:
r0ml has an incredibly interesting article up on O'Reilly's ONLamp, Calculating the True Price of Software, wherein he applies an options pricing model to software cost.
I'll include a larger excerpt than Robert did:
Those who have suggested that open source and free software is somehow not capitalistic, destroying the value of software and other such assertions, have missed this alternative explanation. It is just as likely that the free and open source software folk have stumbled across the financial engineering insight that a significant portion of the value of software is the embedded "derivatives"--options or warrants--on future maintenance and enhancement. Whether one believes that software has intrinsic value is related mostly to one's view on the correct value to use for volatility in calculating the option value. Larger values of volatility mean the software itself is worth less. Smaller values of volatility reduce the option price, and the software is intrinsically worth more.
Therefore, the major difference in worldview between open source advocates and proprietary software license advocates is explainable as a differing opinion on the correct value of the volatility of maintenance and upgrade pricing. People who believe that the pricing on maintenance is stable and unlikely to change see greater intrinsic value in the software. People who fear that the pricing is subject to large fluctuations see no intrinsic value in the up-front license; stripped of the options, the license value approaches $0.
For the open source movement, perhaps a better way to position the change that OSS is making is this: we're converting warrants on future maintenance and enhancements into options, which means that instead of having a sole supplier (warrants), we have created a third-party market (options) of these derivatives.
One of the biggest reasons that I became interested in open source was the "Raiders of the Lost Ark" problem, which is summarized like this. Company develops great software. Software is under-appreciated by the market. Company goes out of business. Future versions of the software are not forthcoming. Imagine the tapes/flopplies/hard drives/CD's/DVD's/whatever being wheeled into a huge warehouse (like at the end of Raiders) and having the doors slammed shut. How much is that great software worth now? Subscription pricing doesn't help, because you still can't guarantee that that the company won't go out of business.
As I've written before, I've no problem paying for software. But I'm not paying for the software that I got. I'm paying to make sure that there's a future for that software. That means supporting the authors/community/organization that developed that software.
![Other blogs commenting on this post](/py-bin/images/bubble.gif)
Both in the ROTLA sense you mention, and also in the sense of needing to keep coders in keyboards. The ROTLA argument targets the corporate, but my point targets the individuals.
I go home and enjoy a few mad stylings in Python that I hope to someday release/unleash, but there isn't much hope of that ever servicing the mortgage.
Posted by Chris Smith at Tue Jul 26 05:33:52 2005
I agree that mad styling in one's spare time is not going to pay the mortagage, but I'm interested in ways for people to make a living doing open source stuff, and for better or worse, there's going to be a threshold for that.
I've paid for plenty of software that was done by companies that went out of business and left my data locked in cold storage. I would have been happy to pay for said software even if it had been open source. In fact, knowing what I know now, I would have paid more money. Software that doesn't improve is worthless to me. I know that from experience.
Posted by Ted Leung at Tue Jul 26 23:08:32 2005
Posted by Trackback from Navarik Windward: shipping software weblog at Fri Jul 29 07:52:42 2005
![RSS Feed for comments](http://www.sauria.com/py-bin/images/xml.gif)
To insert a URI, just type it -- no need to write an anchor tag.
Allowable html tags are:
<a href>
, <em>
, <i>
, <b>
, <blockquote>
, <br/>
, <p>
, <code>
, <pre>
, <cite>
, <sub>
and <sup>
.You can also use some Wiki style:
URI => [uri title]
<em> => _emphasized text_
<b> => *bold text*
Ordered list => consecutive lines starting spaces and an asterisk