<?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: TrollTech, Qt, and Dual-licensing</title>
	<atom:link href="http://adterrasperaspera.com/blog/2005/04/25/trolltech-qt-and-dual-licensing/feed" rel="self" type="application/rss+xml" />
	<link>http://adterrasperaspera.com/blog/2005/04/25/trolltech-qt-and-dual-licensing</link>
	<description>Transmissions from the Little Blue Marble</description>
	<lastBuildDate>Mon, 30 Jan 2012 15:29:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: brockers</title>
		<link>http://adterrasperaspera.com/blog/2005/04/25/trolltech-qt-and-dual-licensing/comment-page-1#comment-65</link>
		<dc:creator>brockers</dc:creator>
		<pubDate>Mon, 25 Apr 2005 09:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.adterrasperaspera.com/blog/2005/04/25/trolltech-qt-and-dual-licensing/#comment-65</guid>
		<description>Your post pretty well covers the reasons for the success of dual licenses in the free software world.  Sun dual licenses Star/Open Office, AOL dual licenses Netscape/Mozilla, etc..  The result is that commercial companies get a revenue stream without having to compete against their own product (via a BSD style license.)  In addition they have the added benefit of incorporating outside development (which are generally unpaid), a solid channel for feedback (and even improvements), and expanded adoption of their product line. 

The other practical benefit to GPL&#039;ed software is the amount of code duplication that is minimized.  It is a common mis-conception that free software is more likely to fork, but the reality of the situation is that when GPL&#039;ed software forks almost all development quickly follows the better development tract.  Thereby code forks when its actually BEST for it to fork and then quickly re-combines.  What does happen is that you get more code reuse.  This is the basic argument that Novell used when porting their Netware environment to Linux.  They decided it made no sense to invest huge sums of money in operating system development when a free option existed that they could use, extend, and reap any future benefits from.  They could do more with fewer developers because they were not competing on the OS level, but on the services they offered on the OS.</description>
		<content:encoded><![CDATA[<p>Your post pretty well covers the reasons for the success of dual licenses in the free software world.  Sun dual licenses Star/Open Office, AOL dual licenses Netscape/Mozilla, etc..  The result is that commercial companies get a revenue stream without having to compete against their own product (via a BSD style license.)  In addition they have the added benefit of incorporating outside development (which are generally unpaid), a solid channel for feedback (and even improvements), and expanded adoption of their product line. </p>
<p>The other practical benefit to GPL&#8217;ed software is the amount of code duplication that is minimized.  It is a common mis-conception that free software is more likely to fork, but the reality of the situation is that when GPL&#8217;ed software forks almost all development quickly follows the better development tract.  Thereby code forks when its actually BEST for it to fork and then quickly re-combines.  What does happen is that you get more code reuse.  This is the basic argument that Novell used when porting their Netware environment to Linux.  They decided it made no sense to invest huge sums of money in operating system development when a free option existed that they could use, extend, and reap any future benefits from.  They could do more with fewer developers because they were not competing on the OS level, but on the services they offered on the OS.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

