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 …
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.
No, you have failed to understand how either license works. Companies are forced to contribute back in the case of the GPL and the project can choose to accept that or not. In the case of the BSD license companies can choose whether to contribute back and if they do, then the project has the option to accept it or not. The GPL makes it always the choice of the project, while the BSD makes it always the choice of the company.
You have failed to understand the difference between idealism and practice. There are more companies that use Linux without ever contributing back than those that do. Those that do do so because it makes practical business sense to improve the upstream project they rely on. Any company that has decided they don’t want to share some code just builds it in a binary module, firmware, or application to sit on top.
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.
No, you have failed to understand how either license works. Companies are forced to contribute back in the case of the GPL and the project can choose to accept that or not. In the case of the BSD license companies can choose whether to contribute back and if they do, then the project has the option to accept it or not. The GPL makes it always the choice of the project, while the BSD makes it always the choice of the company.
You have failed to understand the difference between idealism and practice. There are more companies that use Linux without ever contributing back than those that do. Those that do do so because it makes practical business sense to improve the upstream project they rely on. Any company that has decided they don’t want to share some code just builds it in a binary module, firmware, or application to sit on top.