9 ms·
Why you shouldn't use the Lesser GPL for your next library
- Shorel 13y ago> Proprietary software developers have the advantage of money; free software developers need to make advantages for each other. This actually confuses 'libre' with 'gratis'.
- morbius 13y agoI actually think it's a subtle admission that it's impossible to gain any significant amount of revenue by "selling" free software. I love the open-source/libre philosophy but it's not viable for a business. I think the more pressing question is whether software even should be a business. Many think that there's a certain rift between users and developers that still exists today, and I have to agree. 1. Users push for increased ease-of-use 2. Developers implement more simple systems 3. Power users complain about the loss of features 4. Developers add back in missing features 5. All users complain about software being a convoluted mess The programmer is now left at a disadvantage: he can either continue working with a codebase that's disorganized and inelegant, or he can start over from scratch. In a business environment, starting over from scratch would not be an economically viable situation, while continuing with the older codebase would be the wiser choice (even thought it may piss off users). Users are left disadvantaged; they can continue to use the older software versions but run the risk of poor security and an inferior interface. With free/libre software this problem disappears, as a talented programmer with the user's interest can simply fork the older version and continue to implement a better interface and security updates while retaining a cleaner codebase. However, the endless stream of forks fragment software and hinder unified progress. Also, the original developer is more likely to abandon the software application due to lack of funds and interest. It's a lose-lose situation. There is no one perfect development methodology. The open-source philosophy is more effective in the long run, but proprietary software is the only viable method to sustain a business. Open-source advocates will often point to Red Hat as a counter-example, but it's important to note Red Hat is the exception to the rule. It's also even more important to note that Red Hat isn't doing so hot these days, either. Where the FSF falls down is in its inability to compromise. A number of companies have achieved success with a mixed closed/premium source model, such as JetBrains. While this again allows much more freedom than a standard proprietary setup, the FSF will always refuse to acknowledge any software with ANY proprietary bits in it. They're now incredibly out of touch with Silicon Valley, and it isn't difficult to see why. They continue their militant and expressive attitude instead of expressing gratitude to those that push OSS forward. Apart from GNU, the GPL and its many variants, the FSF is largely irrelevant. It never had to be that way.
- pavlov 13y agoWhere the FSF falls down is in its inability to compromise They're an ideological foundation. There are already plenty of others who compromise in the name of pragmatism, and there's nothing wrong with that. FSF represents a viewpoint that is constantly under threat from some of the world's richest corporations such as Apple. If they became the "Free And Also Not-So-Free (As Long As It's Useful) Software Foundation", they can just as well close shop. They're now incredibly out of touch with Silicon Valley Certainly this is a positive thing in the long run? There's much more to technology than just the Valley players' interests.
- morbius 13y agoMy frustration doesn't stem from the FSF's stubbornness; my frustration stems from the fact that they don't realize how it's holding free software back. The EFF has been very successful at accomplishing their goals because they, unlike the FSF, understand diplomacy and relationships.
- pavlov 13y agoI can't really see how non-GPL free software has been held back. If anything, it's been successful beyond most people's dreams. Most servers are powered by software under Apache and MIT licenses; companies pick what they want and mostly don't give back. The dominant operating system on personal devices is Android, which is free but nevertheless deeply tied with a corporation's interests and developed in secrecy using the same principles as proprietary software. What would FSF gain by supporting that kind of software freedom, other than a reputation as nice guys? That model of freedom has already won, and from FSF's point of view, it's not much better than traditional closed software.
- eridius 13y agoImagine what it would be like if the FSF had been helping instead of fighting this type of open source development?
- 13y ago
- tytso 13y agoThe problem with the readline library example is that there are BSD versions of the library. So you can do something like this: https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/lib/ss/get_readline.c https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/lib/s... https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/lib/ss/listen.c https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/lib/s... So riddle me this. The ss library is under an MIT-style copyright license. Suppose you have a proprietary program (Say, the Solaris kerberos v5 administration daemon client, to take a not-so-hypothetical example). Now suppose it dynamic links against a version of libss that might dlopen readline, or might dlopen editline, and if neither is available, libss will fall back to fgets. Now suppose Solaris distributes their kadmin program independent of the version of libss distributed as part of e2fsprogs. Quick! Is there a copyright violation, and if so, who committed it?
- dllthomas 13y agoThere are now BSD versions of the library. This was not true for several years, after the license was picked.
- yuhong 13y agoYea, this is an old article.
- mzs 13y agoI wonder what changed? "Updated: $Date: 2014/04/12 12:39:52 $" Maybe someone could look in archive.org, it's blocked for me.
- LukeShu 13y agoThe CVS log of the page: http://web.cvs.savannah.gnu.org/viewvc/www/licenses/why-not-lgpl.html?root=www&view=log http://web.cvs.savannah.gnu.org/viewvc/www/licenses/why-not-... The only change of substance since at least 2001 (when they started using CVS) is the rename of "Library GPL" to "Lesser GPL" (the 2001 version had a notice that the rename had occurred, but the article had not been updated). Most of the changes are adding additional translations, and minor markup changes (the most recent is "Remove empty <p> element.")
- trebor 13y agoI don't use GPL libraries because of the tyrannical copy-left clause. If I want to GPL mine, then I'll make that choice. But I won't use a single library that'll force me to choose GPL—I'll just write/find a replacement. So go ahead, make your library GPL instead of LGPL/MIT/BSD/MPL/APL/ETC and it'll sit unused and ignored (for the most part). I also really appreciate what morbius wrote in this same thread: https://news.ycombinator.com/item?id=7757677 https://news.ycombinator.com/item?id=7757677
- davexunit 13y ago> tyrannical copy-left clause Do you believe that proprietary software licenses are tyrannical as well?
- fleitz 13y agoNot really, most proprietary software licenses don't interfere with the ways in which I prefer to release software to clients. Freedom is all about what you want to do, the problem is that GPL developers and developers who sell things to clients have different objectives for what they want to do. Likewise users of paid for software and users of GPL software have very different expectations of the software, GPL users tend to want to modify the code, and paid for software users want the software to work, but don't want to modify it. So for a GPL developer GPL code is very free, for a non-GPL developer it's not very free.
- mbreese 13y agoTo continue with that line of thought... For non-GPL developers, GPL code can even be more expensive than the cost of a proprietary library.
- zAy0LfpBZLC8mAC 13y agoWell, but using your needs as the defining criteria for freedom is not particularly universal, is it? If a customer of mine requires that I provide them with the ability to use and modify the system I build for them in any way they want, proprietary licenses are quite "tyrannical" (though I wouldn't really use that word), whereas GPL gives me the freedom to do what I want/need to do. Which also seems to highlight a possible confusion on your part, that somehow "paid for software" is the opposite of "GPL software". When I sell software, customers tend to want to be able to modify it, or to have the ability to have others implement modifications for them. And that works both with proprietary code as well as with GPLed code: It's no problem at all to sell code under a proprietary license that allows modifications for own use, but it's also no problem at all to sell code under the GPL, which also allows modifications, and at the same time allows me to build on GPLed code. Also, I don't think terms such as "GPL developer" make much sense. There just is code out there that you can use under different licenses, some of which are incompatible, and for a given project, you have to take care to select components that are compatible technically as well as legally, both between them and with the requirements of the project--and in particular, there isn't really anything all _that_ special about the GPL, as you cannot include proprietary code in a project when the license is not compatible with the customer's requirements either.
- josephschmoe 13y agoThe problem, I think, with the GPL community is that they refuse to accept that almost all software developers make a living by working for a company, and feel that it is unjust to refuse their libraries to others who do the same. And, because their software is open source, someone will inevitably create a better competing library based on the ideas behind the GPL one. That new library? Apache license.
- outside1234 13y agoThis. There is the ivory tower and the real world, and in the real world, the license can't be GPL.
- fdej 13y agoLinux (sorry, GNU/Linux) is ample evidence to the contrary.
- superuser2 13y agoNo it's not. Linux is useful and used all of the time in proprietary systems because there are lots of useful classes of things you can do with linux that aren't derivative works. There are no useful things you can do with a library besides link it.
- pessimizer 13y agoOther than use it in Linux and GPLed software, software which offers lots of useful classes of things that you can do with them that aren't derivative works.
- outside1234 13y agoHe was talking about libraries, not platforms. Sorry I should have made that clear.
- dllthomas 13y agoWhile it's true that GPL is often incompatible with specific strategies chosen by companies (and often those are the most effective strategies in the current environment, and maybe in any reasonable environment), there is still a tremendous gulf between GPL - which permits commercial uses that abide by its restrictions - and anything with a non-commercial clause. Not that this entirely undermines your point, just promoting deeper awareness/understanding of the issues.
- benatkin 13y agoThe title would be perfect for an article arguing for a non-copyleft license instead of the LGPL. Some who create projects mistakenly believe that if they use the LGPL or some other copyleft license that most of the problems with the GPL go away. I think Firefox has lost some developers to Chromium because of Chromium's simpler license. The EPL is also frustrating to some who would like to use Clojure (Scala is under a simpler license). I tried writing such an article: https://gist.github.com/benatkin/98e28b329842f021e6d3 https://gist.github.com/benatkin/98e28b329842f021e6d3
- zmoazeni 13y agoIt took some time for me wrap my brain the restrictions around the EPL while I was picking up clojure, but I don't understand how EPL would be frustrating to other developers or businesses. Could you elaborate? As I understand it, as long as you use a library according to its stated API, you can do whatever you want with it and license the entire product under any license you choose. [1] [1] - https://www.eclipse.org/legal/eplfaq.php#EXAMPLE https://www.eclipse.org/legal/eplfaq.php#EXAMPLE
- danray 13y agoGood points in this article. Note as well that the LGPL requires you to permit reverse-engineering of your proprietary code. There are good reasons for this, but it's unrealistic in a lot of organizations. A lot of developers (and a lot of lawyers!) rely on the rule of thumb that you're fine under the LGPL as you don't modify and don't statically link. That's a fine rule of thumb, but that's all it is.
- enjoy-your-stay 13y agoI thought one of the main reasons for the LGPL was to attract more people to use and contribute to your library, whether open source or proprietary; with the added advantage that developers efforts were not being wasted with needless duplication. This approach seems to seek to create a much stronger 'us' and 'them' mindset which can only alienate a large number potential contributors.
- zAy0LfpBZLC8mAC 13y agoOne could also look at it as seeking to avoid needless duplication even more: By trying to give free software an advantage by being able to make use of GPLed libraries, or possibly to motivate people to release their new software under GPL because that allows them to make use of GPLed libraries, you might be able to avoid future work on the competing proprietary silos, instead focusing resources that are used for developing the particular kind of software on the one commonly developed free software solution, thus creating a much stronger 'us all together' instead of any kind of 'us' vs 'them'.
- jeena 13y agoI'm really happy there are people fighting for a world like this. It doesn't matter that they can't get 100% of the market, just by advocating for a better alternative makes the whole thing better.
- nitrogen 13y agoPragmatically, the FSF should be advocating for the LGPL over BSD or Apache, since GPL over LGPL is already a lost battle.
- cpeterso 13y agoWhat's the difference between Mozilla supporting EME to maintain market relevance among proprietary competitors and the FSF licensing glibc as "Lesser GPL" to do the same?