With a recent change that removed dialog in favor of bsddialog, FreeBSD has now retired the last piece of GPL-licensed code in its base system. Although the impact of this change will be minor for …
You are very shrilly yourself. Plenty of companies have shown it isn’t hard to take GPL without contributed back. There are high odds you are using a chrome based browser to read this - did you know that is a GPL project because once upon a time it was khtml (from the KDE project), but the changes were never contributed back. Many embedded companies have their own fork of linux as well - their changes are all available as the GPL requires, but the changes won’t be accepted to the kernel as is and so the fact that they are available is useless.
Meanwhile there are many companies using FreeBSD who choose to contribute their changes back, just like some companies choose to contribute back to various GPL projects they use.
Basically his argument is that because some companies choose to contribute back to BSD projects even though they aren’t required to, and because some GPL projects choose not to merge some changes from downstream forks, the GPL and BSD licenses are effectively the same. I think the flaw in this logic should be pretty apparent. I think the GPLv2 vs. GPLv3 debate is a lot more interesting, particularly since Linus has come out against GPLv3.
Another way to phrase that is that companies can choose to meaningulfully contribute back, or not, with either project, and there are plenty of examples of each combination.
You are very shrilly yourself. Plenty of companies have shown it isn’t hard to take GPL without contributed back. There are high odds you are using a chrome based browser to read this - did you know that is a GPL project because once upon a time it was khtml (from the KDE project), but the changes were never contributed back. Many embedded companies have their own fork of linux as well - their changes are all available as the GPL requires, but the changes won’t be accepted to the kernel as is and so the fact that they are available is useless.
Meanwhile there are many companies using FreeBSD who choose to contribute their changes back, just like some companies choose to contribute back to various GPL projects they use.
So your argument is that because there are some exceptions to a rule, the opposite of that rule is true.
Basically his argument is that because some companies choose to contribute back to BSD projects even though they aren’t required to, and because some GPL projects choose not to merge some changes from downstream forks, the GPL and BSD licenses are effectively the same. I think the flaw in this logic should be pretty apparent. I think the GPLv2 vs. GPLv3 debate is a lot more interesting, particularly since Linus has come out against GPLv3.
Another way to phrase that is that companies can choose to meaningulfully contribute back, or not, with either project, and there are plenty of examples of each combination.
Rocks are woke now.
Yeah, since rocks went all woke and stuff, they have really been rolling down hill…
My sediments exactly
Honestly this is magnificent. 🤡