3 ms·
Readline being GPL was actually a pretty good idea imo– it's gotten some pieces of software to open-source themselves solely because they wanted to use readline
by _delirium 14y ago
Readline being GPL was actually a pretty good idea imo– it's gotten some pieces of software to open-source themselves solely because they wanted to use readline (the clisp implementation of Lisp is the most famous example). Seems like a reasonable quid pro quo: you want to use my nice open-source library, then you need to open-source also.
- dragonwriter 14y ago<blockquote>Readline being GPL was actually a pretty good idea imo– it's gotten some pieces of software to open-source themselves solely because they wanted to use readline</blockquote> That's pretty much the entire value proposition of the GPL, and it was pretty important in the early days of F/OSS when the value propositions of F/OSS was less clear -- "you have to open your stuff if you want to use my stuff". But very early on in F/OSS, the argument was made that F/OSS was actually good for the people releasing their software as F/OSS -- not just good for the downstream recipients. And to the extent that that value proposition has been accepted, GPL-style licensing is less beneficial. If you believe that F/OSS is good for the licensor as well as the licensee, there is no reason, as a licensor, to use the license on your software as a bribe to get other people to open their software. While initially -- before lots of big players clearly saw the value of F/OSS and adopted it for things they released even outside of GPL-style license-based compulsion -- the GPL was useful both for those who believed in the value proposition of F/OSS and those who were ideologically attached to F/OSS independent of the value proposition, its now useful mostly to the latter group and a negative to the former.
- lucian1900 14y agoBut recently, GPL libraries have mostly only inconvenienced other open source projects, like Racket not shipping readline. That tactic is dead.