2 ms·

> you'd probably be running some form of BSD :) You mean macOS? Or Playstation 3/4? Proprietary, non-free form of BSD, yes.

nix23 4y ago
You use unfree Linux too...for example google. What people seam to forget, under GPL you don't need to give your code back if your DON'T redistribute it. And that's why google forbids the use of AGPL internally. >You mean macOS? https://github.com/apple/darwin-xnu https://github.com/apple/darwin-xnu Why dont you know that? If your a apple user and so interested in opensource?
Gud 4y ago
Why wouldn’t you be using one of the many freely distributed BSDs if software freedom is so important to you? That’s what I do, anyway.
aforwardslash 4y ago
You mean macOS? > The relevant parts of macOS for this discussion are actually opensource (kernel & most userland utilities), albreit not updated often; > Playstation 3/4? Does the fact that product XYZ has a BSD-based product reduces or affect the continuity of the opensource project? No, it doesn't. And that is the beauty of BSD. Some companies build closed source products on it, some companies actually give back contributions (such as Netflix). Its fine either way. > Proprietary, non-free form of BSD, yes. Well, Microsoft used BSD code to some extent in previous versions of Windows (afaik tcp stack, services for unix, ftp client, etc). On the other hand, I do use Android-based devices - which are, for practical purposes, mostly a generic non-free form of Linux. In fact, not only the source code (when you can get it easily) is almost useless for practical use, but often bootcode and drivers are proprietary signed blobs - without which the device is just a fancy brick. Also, I'd argue there is little value brought into the linux project just because it is a core Android component. How is this scenario different from a "non-free form of BSD"?
- ryao 4y ago
  > Does the fact that product XYZ has a BSD-based product reduces or affect the continuity of the opensource project? No, it doesn't. And that is the beauty of BSD. Some companies build closed source products on it, some companies actually give back contributions (such as Netflix). Its fine either way. The irony of the GPL is that it does not require giving back. The only requirement is to provide source code when you do binary distribution. There is no provision about giving back to the upstream developers. Forced code dumps are not giving back and projects like Linux do not consider them to be a form of giving back. Sending useful patches and responding to maintainer feedback would be giving back. The GPL is no better at obtaining that than a 2-clause BSD license.
ryao 4y ago
> You mean macOS? Or Playstation 3/4? Proprietary, non-free form of BSD, yes. As someone who has been dedicated to OSS since I started writing software and also wrote some proprietary code for the health care industry (which was not open sourced mainly because there was no point since it would have been a code dump useless to people because hardware patents were involved), I have this feeling: I would rather good code be reused by proprietary stuff, because someone is going to put that code in systems where failures kill people and it is better that they reuse good code to prevent deaths. It is ridiculous to embrace a philosophy in software licenses where people dying because of your decision to deny good code to people writing proprietary software is okay. The OSS versus proprietary debate should not be done in a manner that causes fatalities.

nix23 4y ago

You use unfree Linux too...for example google. What people seam to forget, under GPL you don't need to give your code back if your DON'T redistribute it. And that's why google forbids the use of AGPL internally. >You mean macOS? https://github.com/apple/darwin-xnu https://github.com/apple/darwin-xnu Why dont you know that? If your a apple user and so interested in opensource?

Gud 4y ago

Why wouldn’t you be using one of the many freely distributed BSDs if software freedom is so important to you? That’s what I do, anyway.

aforwardslash 4y ago

You mean macOS? > The relevant parts of macOS for this discussion are actually opensource (kernel & most userland utilities), albreit not updated often; > Playstation 3/4? Does the fact that product XYZ has a BSD-based product reduces or affect the continuity of the opensource project? No, it doesn't. And that is the beauty of BSD. Some companies build closed source products on it, some companies actually give back contributions (such as Netflix). Its fine either way. > Proprietary, non-free form of BSD, yes. Well, Microsoft used BSD code to some extent in previous versions of Windows (afaik tcp stack, services for unix, ftp client, etc). On the other hand, I do use Android-based devices - which are, for practical purposes, mostly a generic non-free form of Linux. In fact, not only the source code (when you can get it easily) is almost useless for practical use, but often bootcode and drivers are proprietary signed blobs - without which the device is just a fancy brick. Also, I'd argue there is little value brought into the linux project just because it is a core Android component. How is this scenario different from a "non-free form of BSD"?

ryao 4y ago
> Does the fact that product XYZ has a BSD-based product reduces or affect the continuity of the opensource project? No, it doesn't. And that is the beauty of BSD. Some companies build closed source products on it, some companies actually give back contributions (such as Netflix). Its fine either way. The irony of the GPL is that it does not require giving back. The only requirement is to provide source code when you do binary distribution. There is no provision about giving back to the upstream developers. Forced code dumps are not giving back and projects like Linux do not consider them to be a form of giving back. Sending useful patches and responding to maintainer feedback would be giving back. The GPL is no better at obtaining that than a 2-clause BSD license.

ryao 4y ago

> You mean macOS? Or Playstation 3/4? Proprietary, non-free form of BSD, yes. As someone who has been dedicated to OSS since I started writing software and also wrote some proprietary code for the health care industry (which was not open sourced mainly because there was no point since it would have been a code dump useless to people because hardware patents were involved), I have this feeling: I would rather good code be reused by proprietary stuff, because someone is going to put that code in systems where failures kill people and it is better that they reuse good code to prevent deaths. It is ridiculous to embrace a philosophy in software licenses where people dying because of your decision to deny good code to people writing proprietary software is okay. The OSS versus proprietary debate should not be done in a manner that causes fatalities.