7 ms·
> This is wrong. Copyleft licenses are concerned with freedom, not price. Precisely. The thought that someone might take the code I wrote and make it into a pr
by TazeTSchnitzel 11y ago
> This is wrong. Copyleft licenses are concerned with freedom, not price.
Precisely. The thought that someone might take the code I wrote and make it into a proprietary product, removing the freedoms I had, is horrible. But if someone made an free software product based on it and made millions, all the better for them!
- reitanqild 11y ago> The thought that someone might take the code I wrote and make it into a proprietary product, removing the freedoms I had, is horrible. I feel this argument is weak: even if I license my works under BSD, no one can make my BSD licensed code that has already been distributed into to a proprietary product, even not myself. To make that software that I licensed under BSD a proprietary product they would need to somehow convince all users of my software to get rid of all copies as well as convincing me to stop distributing it under a free licence. Building a proprietary product that includes my code does NOT remove anyones freedom to use my code, no?
- Deejahll 11y agoThis presumes that any modifications to "your" code that someone else makes should be none of your business. Seems fine on the surface. But what if your code writes files or communicates over the network? And what if, say, Microsoft takes your permissively-licensed code that is just beginning to gain popularity, changes one piece of it to make it incompatible with yours, and doesn't release their change? They use their massive marketing department or pre-bundling to get lots of Windows users to use it. Everyone is still free to use "your" version of the code, but nobody wants to, since it is incompatible with the more popular Microsoft version, now on its way to becoming "the standard." If you are okay with that, no rabid copyleft zealot like me has any place to criticize you. Release your code with a permissive license. That's fine. (Permissive licenses are considered "Free Software" by FSF and rms as well, after all.) But to me, that seems grossly unfair for code I spent my valuable time designing and developing, so I don't release my code under a permissive license. If Microsoft wants to build a product with the work I have done, it needs to convey the same freedoms to its users that I did. That's the cost.
- geon 11y agoA very contrived example.
- Deejahll 11y agoOh yeah I just pulled that from a fever dream I had, that sort of thing never happens in real life. > "Embrace, extend, and extinguish", is a phrase that was used internally by Microsoft to describe its strategy for entering product categories involving widely used standards, extending those standards with proprietary capabilities, and then using those differences to disadvantage its competitors. https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish
- jahewson 11y agoAnd what permissively licensed software did Microsoft apply this policy to, exactly? Or is it just an unfounded fear?
- anonbanker 11y agoKerberos. back in 2000.
- fao_ 11y agoRead the link. It has a moderately-sized list of examples from Microsoft. https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish#Examples https://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish...
- throwawaykf05 11y agoI could not find a single example of "permissively licensed software" in there. Nor do in think one exists. Remember, this is the Microsoft that would not touch open source with a 10-foot pole. MS did embrace and extend standards, but that is a very different thing from code.
- morganvachon 11y agoBSD doesn't remove any freedoms from the original software author, and in fact it unshackles them from having to publish all future development, allowing them to go proprietary in the future if they wish to. To put it another way, once you license something under GPL, it is forever GPL. That's a strength of that license in the sense that it has allowed so much excellent and important software to grow and flourish. On the other hand, when you license something under BSD, at any point you have the power to take it to another license or make it proprietary. That's the "permissive" part that many people (including GPL advocates) don't get. The source code itself is still open as long as the original author wishes it to be. Under the GPL, the source code is open for all eternity, even if the original author changes her mind later. Another aspect of this (and it was mentioned elsewhere in this discussion) is that, even if a company comes along and turns your BSD licensed code into their own proprietary product, you still get to keep your code and continue to improve it. All they've really done is forked it; if they are a good citizen they will even contribute improvements back to you. I think the classic example of this is Mac OS X, which is based in part on FreeBSD. When Apple forked FreeBSD into the base of their new commercial OS, the FreeBSD project didn't magically disappear. Here we are 15 years later and both the commercial OS X and the open source FreeBSD are flourishing. Development of FreeBSD didn't die the day OS X was born.
- gbog 11y agoOk but I would like to know if Mac os taking FreeBSD code did benefit to Free BSD. Edit: tried to add more but some js breaks everything on my phone
- toast0 11y agoOS X uses the FreeBSD userland, but it was more or less a one time pull, the kernel is radically different, so it would be hard to keep things synced; as a result, I doubt there has been a lot of contributions of patches backwards. However, Apple and FreeBSD both had license problems with gcc, and Apple sponsored LLVM, which benefits FreeBSD as well. Maybe there's a cultural benefit for FreeBSD as a result of OS X exposing people to the FreeBSD userland, although running into limitations that have been fixed upstream more than ten years ago may give people the wrong ideas.