You don't need to re-license permissively licensed software to include it in your code.

Apple, as far as I know, doesn't release the FreeBSD fork they use in Mac OS.

Companies generally use a ton of permissively licensed software and don't release forks of it under any license because the entire point of the license is that you can take the code, make modifications, and you have no obligations to give anything back when doing so.

There was an attempt to rebrand "free software" -- meaning software focused on user freedom -- as "open source" -- referring to software permissively licensed for use by corporations. This was the point of the OSI. [0]

> The “open source” label was created at a strategy session held on February 3rd, 1998 in Palo Alto, California, shortly after the announcement of the release of the Netscape source code....The conferees believed the pragmatic, business-case grounds that had motivated Netscape to release their code illustrated a valuable way to engage with potential software users and developers, and convince them to create and improve source code by participating in an engaged community. The conferees also believed that it would be useful to have a single label that identified this approach and distinguished it from the philosophically- and politically-focused label “free software.” Brainstorming for this new label eventually converged on the term “open source”, originally suggested by Christine Peterson.

So literally a decision by a committee of industry folks to play down the idea of freedoms or giving back and focus instead on the business case.

So they killed the ethical argument that favored copyleft licenses in favor of the business argument that favored permissive ones.

Now people are saying "hey it's unfair that you're not giving back." Fair enough, but that's an ethical argument. That's what the OSI was trying to get rid of.

The OSI approach has its place. We wouldn't have Mac OS or Google or Meta without it. But its place is allowing industry to standardize and to reduce costs. Those benefit consumers indirectly since we have fewer competing standards and reduced development costs can imply reduced end user costs. But that only works because each company can make improvements and exclude others from using those improvements; i.e. they can make proprietary improvements.

[0] https://opensource.org/history

Wake up. That's what's happening to your gifts you released under permissive licenses. Enterprises like AWS, Apple etc. build their business on them and don't want to give anything back.

> I find this comment to be incredibly disingenuous, and just plain false.

I wonder if there will be any justification for this remark :-)

> Excluding people would only be done if someone took a permissive license and then re-licensed it to something more closed

Yes, that is the only way they can be distinguished. If nobody ever distributes proprietary software including the permissively-licensed code, then it might as well be copylefted.

> you've entirely made up a malicious assumption about what people do with the software. And you're even assuming people ARE doing something like this with the software.

I think this is your point of departure with reality. This happens constantly! Anyone who ever includes permissively licensed code in a proprietary codebase is denying the users of that codebase from the freedoms the upstream developers gave them. The freedom to do this is the freedom to withhold rights from other people. You can choose not to care about that, if you want. But that's what is happening.