
June 25th, 2006, 11:36 PM
|
|
Contributing User
|
|
Join Date: Mar 2005
Location: Boston, MA
|
|
|
Concerns about gpl terms
I have been doing some reading up on Linux and the GPL, and I have some concerns about the GPL terms that I was hoping somebody could address. I've read the full license, but I'm still a bit confused as to what constitutes a derivative work.
For example, if I were to write a program designed specifically for the Linux operating system, would I have to license it under the GPL just because it is designed to work on an operating system / kernel that is under the GPL?
If that is not automatically the case, then what if the software needed to make use of dynamically linked libraries? This is done all the time in Linux, and is in fact one of the main features of the OS. Does the mere use of libraries included in GNU/Linux require the entire software to adopt the GPL?
Finally, what about the programming language itself? Many programming languages seem to be released under the GPL these days. Does that mean that any software programmed using those languages also has to be GPL'ed if it is distributed?
I used to be a big fan of the GPL as an amateur developer, but now I'm not so sure that I like it. Steve Ballmer described it as "viral" and while it might get me in some trouble here, I can see where he's coming from - it certainly seems like it would have a chilling effect on development if you can't retain the exclusive rights to your code for a period of time. Yes, the GPL doesn't keep people from selling their products, but it is very obvious that when you have to grant your customers redistribution rights, you can't charge much more than the basic transaction costs of burning a CD or offering a download, which are basically zero these days. Also, while you can charge for support, it almost seems like that would encourage you to make an error-ridden product - but then nobody would buy it. The BSD model seems a lot better...
Anyway, while I am not exactly close to the level of expertise where I can make software for sale, I do aspire to reach that level, and the GPL is increasingly worrying me. So I guess my main questions are:
1. Is it possible to make proprietary software for use on a GPL operating system (i.e. Linux)?
2. Is it possible for proprietary software to use operating system libraries that are under the GPL?
3. Is it possible for proprietary software to be built on a GPL programming language?
Edit: Also, how can I figure out what the licensing terms are for "classic" programming languages like C?
Thanks...
|