BSD licence allowed to work with the AT&T licence which at the end generated all the drama. Unix wars.
Again BSD is great if you don’t care about what will happen with your code.
Yeah the Android point doesn’t have any sense, that’s right.
Apple shares the code of the parts they want. Since it’s not a copyleft licence, then they can still ship you a version of Darwin + privative code as your macOs without sharing the entire code. So you end running kind of Frankenstein program with parts you don’t know what they do.
AOSP is not a great licence because it allows Google benefit from contributions, but then it has tons of privative software on top. So basically contributing to the AOSP means that you improve the code that later it’s used in combination with privative one.
My point is that libre source code should enforce that derivations of it stay libre. Otherwise you are working for free for companies that don’t care about the users.
Hey for companies is a good point. The best system for them is open source. It makes sense for them to use it. And open source is much better than just privative.
From the point of view of the individual user and developer is not that great. It kind of hooks you in because it has open source parts, but you are probably unaware of all the closed source stuff that runs in combination with it.
I get the open source point, but I don’t find it fair at the long term for the individual developer and user.
Over the years I’ve become convinced that the BSD license is great for code you don’t care about. I’ll use it myself. If there’s a library routine that I just want to say ‘hey, this is useful to anybody and I’m not going to maintain this,’ I’ll put it under the BSD license.
Even for BSD, there’s an incentive to share your code to upstream. Otherwise you will have to maintain a separate branch or fork and that can take a lot of effort.
BSD licence allowed to work with the AT&T licence which at the end generated all the drama. Unix wars.
Again BSD is great if you don’t care about what will happen with your code.
Yeah the Android point doesn’t have any sense, that’s right.
Apple shares the code of the parts they want. Since it’s not a copyleft licence, then they can still ship you a version of Darwin + privative code as your macOs without sharing the entire code. So you end running kind of Frankenstein program with parts you don’t know what they do.
AOSP is not a great licence because it allows Google benefit from contributions, but then it has tons of privative software on top. So basically contributing to the AOSP means that you improve the code that later it’s used in combination with privative one.
My point is that libre source code should enforce that derivations of it stay libre. Otherwise you are working for free for companies that don’t care about the users.
Hey for companies is a good point. The best system for them is open source. It makes sense for them to use it. And open source is much better than just privative.
From the point of view of the individual user and developer is not that great. It kind of hooks you in because it has open source parts, but you are probably unaware of all the closed source stuff that runs in combination with it.
I get the open source point, but I don’t find it fair at the long term for the individual developer and user.
Even for BSD, there’s an incentive to share your code to upstream. Otherwise you will have to maintain a separate branch or fork and that can take a lot of effort.