Why would anyone put anything under the GPL license?
Does this seem retarded to anyone else besides me?! If
its supposed to be “free software” then why does this
license require you to show people all of your code?!
That’s the very meaning of “Free”. This is not free as in beer; we’re
talking “libre”.
And you cant sell it or use it commercially even if
you write a bunch of your own code that links with
it? that sux!!
The idea is to protect the rights of the USER - which could be you! If
you have the source for a program you’re using, you can tweak it if you
need/want, and more importantly, you can maintain the program yourself,
if the original author drops it.
This is incredibly important for companies that develop systems that are
required to work for more than 5 years. Base your system on closed source
software, and you’re screwed if the provider goes bankrupt, or just
decides to stop supporting the software, a few years later.
It seems like a total waste of effort to me if people
cant benefit from using the code/library except for in
another GPL project. I dont see any good in GPL stuff,
in fact I ignore anything GPL!
Then you’re either doing one of the few things that isn’t compatible with
Free/Open Source, or you’re totally missing the point.
LGPL makes way more
sense. If I make anything I will definatly LGPL it for
everyone to use freely, as in free, as in the point of
freedom, to be able to actually use it. I cant believe
they call GPL “free software” - what B.S.!
It’s less free than LGPL in one way, but much more free in another; the
GPL forces you to keep the original code, as well as applications using
it, truly Free. This is in order to protect users from scenarios like
those discribed above.
Both the GPL and the LGPL are meant to protect users/developers from code
being stolen and turned into closed source code. The GPL also protects
the code from being “taken advantage of” by closed source code.
In some cases, some people might just not want campanies to make big
money by writing closed source GUIs for their Free/Open Source
engines/libraries, for example. Then the GPL should be used.
OK so heres my question. what if I want to make a
LGPL version of something, thats based on a GPLed
library?
The LGPL is less restrictive than the GPL, so actually using the complete
solution (the GPL + LGPL code) as a whole under the terms of the LGPL,
would not be legal. The GPLed code is not meant to be called by Closed
Source software in any way - directly or indirectly.
Note that what is seen as “normal use” (ie loading an application on an
OS - which is theoretically a form of linking) is an exception. You are
allowed to run closed source software on the GPLed Linux kernel, for
example. (Later versions have an explicit addition to the GPL to make
this totally clear.)
Its not fair if people GPL everything first!
Why? Do you think you have a right to tell people what licence to use for
their software? Do you think them writing it for anyone to use for
FREE, and to more or less freely reuse in other projects, gives you
more right to complain? Or should id Software automatically be forced
to release the full source of the Q3 engine, just because they have given
you the right to write free (as in beer) mods for it…?
I think not. Take what you get, or hack your own.
Theres only so many ways to load or manipulate a
certain filetype… and you have to learn how to do it
from somewhere. If GPL is supposed to be for
educational purposes, how can you write anything
commercial based on whats in the GPL source, without
releasing the code?! (and no, I dont mean a cut 'n
paste job…)
This is a matter of what “based on” means. Provided Free/Open Source
advocates have become pro software patents all of a sudden, you reading
the source to learn how something works, and then hacking your own
implementation under whatever licence you like, should not be a problem.
I think some people THINK they are helping by making
their projects GPL, but in actality are hurting us
developers since we have to rewrite it over and over
in different ways, to avoid patent problems if we want
sell it…
Here we go; patents? Yeah, I’ve seen the flame wars caused by the RTLinux
patent, but that’s ONE specific case - and we all know now that that
was a very bad idea. I hope we won’t see any more of that stuff,
regardless of the intentions. It just won’t work. 
Where if they just LGPL it, nobody would
have to reinvent the wheel to do something someone
already did properly.
But are you sure everyone that’s thinking about GPL or LGPL wants to
help people that DO NOT want to use Free/Open Source licenses…?
Would you like Microsoft to make money selling closed source software
that links with your Free/Open Source code?
(Do we LIKE to rewrite the same code over and over? I
sure dont!.. and what if the GPL code is the best
way to do it? If we cant use it commercially, dont we
all lose out!?)
No. GPLed software is very different from software patents.
There’s no real problem here; if you’re not happy with the licence,
either hack your own code under a different license, or contact the
copyright holder(s), and see if he/she/they are willing to sublicence the
software to your project under a compatible licence. (The TiMidity code
in SDL is an example of that.)
//David Olofson — Programmer, Reologica Instruments AB
.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------------> http://www.linuxdj.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |
-------------------------------------> http://olofson.net -'On Friday 19 April 2002 16:38, Jason Robertson wrote: