5 ms·
I think this article (and possibly the speaker the article responds to; I haven't seen any transcript or recording yet) misses one of the bigger poitns of permi
by yellowapple 11y ago
I think this article (and possibly the speaker the article responds to; I haven't seen any transcript or recording yet) misses one of the bigger poitns of permissive licensing: the ability for virtually any free software project to reuse your code. As a developer writing a library or somesuch, my concern is often whether or not I'm locking a large number of projects out of making use of my code. Yeah, this means that proprietary software can use it, too, but at least I'm credited for the work (as per the terms of most copyfree/copycenter licenses) and other FOSS projects have the same ability.
This isn't to say that copyleft is automatically bad, but rather that consideration for the general development ecosystem is a worthwhile consideration. If you're a Perl hacker, for example, you're probably going to use "the same license as perl itself" (GPL + Artistic License) or perhaps the Artistic License 2.0 because those are the norms of the Perl community. If you're a Ruby hacker, you're probably going to use the MIT license because that's the most common. If you're writing an Emacs package, you'll probably release it under the GPL. If you're writing an Erlang module, I'd reckon the Apache license nowadays to be the new baseline.
This is also affected by which operating system you're targeting. BSD folks will tend to lean permissive, while GNU/Linux folks will tend to lean copyleft. Windows and OS X folks will tend to lean proprietary or permissive.
In other words, what license to pick really depends on the norms of the platform you're writing for. There's no "wrong" answer here unless the license you choose excessively impedes reusability by the broader community you're operating in, in which case you would be wise to adapt accordingly.
- nickpsecurity 11y agoGood point on how all OSS developers benefit rather than just FOSS. However, the author did address that by noting the permissive licenses goal was mass adoption and FOSS was pushing their notion of freedom.
- yellowapple 11y agoTrue. I got the impression that the specific nuance of benefiting FOSS as much as non-FOSS was being a bit glossed over, though. It's a little bit more nuanced than "mass adoption", too, though. For me (as someone who tends to lean permissive in his software projects), it's more about deduplication of work and making my things as useful as possible for everyone. I'd love for a GPL project or an MPL project or an Apache project or a BSD project or whatever to find enough value in the code I write to not feel that they have to write such code themselves.
- nickpsecurity 11y ago"True. I got the impression that the specific nuance of benefiting FOSS as much as non-FOSS was being a bit glossed over, though." In the original article? Yeah, these people often get so worked up about how proprietary products can benefit that they forget the huge amount of open-source, non-GPL efforts that can draw on the work. Despite the fact that the server traditionally running on every Linux box was an Apache-licensed one who's name I can't recall... jk. In any case, I fully respect your decision to try to help OSS projects avoid wasted work and make something they can all use regardless of license. Similar to those putting work in the public domain. That used to be a badge of pride in developer altruism. Now, the standard license (GPL) for altruism forces the developers will on users of the code. Quite the change OSS went through.
- quadrangle 11y agoShort version: license compatibility problems is a legitimate concern about GPL, separate from the other stuff about proprietary issues.
- arfar 11y agoI think Richard Stallman is (was?) aware of this. He famously condoned Ogg/Vorbis using a BSD license so that it would be more greatly adopted by developers/companies making music players and the like. This was in the face of the patent protected, extremely widely adopted, MP3 format however. https://news.ycombinator.com/item?id=5461004 https://news.ycombinator.com/item?id=5461004