Originally posted by Sergio
View Post
That the code is here doesn't mean its free. What about patents, what about license revoke, what about relicensing and actual protection of the freedom. The first two aspects are usually controlled by separate agreements (outside of BSD), thus BSD code gives you no right to run the code in itself.
If the code is published under open license, no company is limited to use it in how they see it fit.
If its not a backend development tool, library, parts bin or driver - then the market share will be given to the first with higher investment and faster reaction. Think Gates.
If it is a backend development tool, then the company distributing it is almost guaranteed uses proprietary frond-ends to gain the revenue. The BSD-licensed guts is nothing but a pet-project, shifted outside - but not set free. For example, the panels of server administration that make hosting and configuration easy - are all proprietary. The MacOSX - uses a lot of BSD guts, but its all proprietary. This is not free software, its a refracted proprietary.
If its a library, then this library is either promoting generic interface and aiming for maximum compatibility, or its copyright holders don't care where its gonna be used.
The driver case was explained above, they are not getting funds from driver itself, but from service and hardware sells.
All-in-all the code is open, do what you want, no obligations. But :
Unworthy code will be not touched by a company. It will sit slowly as a hobby project and depricate, or rise its worthiness.
If its a worthy code and fits within company agenda, they will think twice before contributing anything back due to the legal costs, unnecessity to do so (loose of time/money over unnecessary negotiations) and loose of competitive advantage. They will tend to keep the changes in best case, and expand/extinguish in the worst case. Even if its an interface, but widely popular, why not salt it with a few features and market it? Think 802.11n 150/300 mbit proprietary channel bindings implementations - they are not compatible with each other.
And if its worthy and they still develop and contribute back - then they have a reason to do so. They either produce proprietary frontends, plugins or similar, and the code in question is not their selling point. In fact, its barely usable to anyone except engineers.
Originally posted by Sergio
View Post
For example, a law against slavery restricts my freedom to capture and work slaves, but preserves the freedom of all potential slaves. The GPL is analogous to a law preventing slavery(of the software). While it does indeed contain restrictions, those restrictions actually encourage more freedom, not less.
Say, is slavery as in "stripping the freedom" acceptable? In your model - it is. In my model - it is not. What you call freedom is in fact - anarchy. Has anarchy EVER been democratic?
Sure, everyone is free to decide what path to take. But the decision will have consequences. Your path is obviously not free software.
Have I missed anything?
Comment