Context:
Permissive licenses (commonly referred to as "cuck licenses") like the MIT license allow others to modify your software and release it under an unfree license. Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.
Andrew Tanenbaum developed MINIX, a modular operating system kernel. Intel went ahead and used it to build Management Engine, arguably one of the most widespread and invasive pieces of malware in the world, without even as much as telling him. There's nothing Tanenbaum could do, since the MIT license allows this.
Erik Andersen is one of the developers of Busybox, a minimal implementation of that's suited for embedded systems. Many companies tried to steal his code and distribute it with their unfree products, but since it's protected under the GPL, Busybox developers were able to sue them and gain some money in the process.
Interestingly enough, Tanenbaum doesn't seem to mind what intel did. But there are some examples out there of people regretting releasing their work under a permissive license.
Not all of us write code simply for monetary gain and some of us have philosophical differences on what you can and should own as far as the public commons goes. And not all of us view closed derivatives as a ontologically bad.
Please explain how allowing a third-party to limit computer users' ability to control and modify their own property is anything other than ontologically bad?
If I release something free of restrictions to the world as a gift, that is my prerogative. And a third party's actions don't affect my ability to do whatever I want with the original code, nor the users of their product's ability to do what they want with my code. And the idea of "property" here is pretty abstract. What is it you own when you purchase software? Certainly not everything. Probably not nothing. But there is a wide swath in between in which reasonable people can disagree.
If you are an intellectual property abolitionist, I doubt there is much I can say to change your mind.
I'm not convinced something being your "perogative" and it being "ontologically bad" are mutually exclusive, so I don't see how that's a rebuttal.
I want to know why you think it isn't bad, not why you think you're allowed to do it.
Because I don't know why it is closed source. Is it a personal project? A private project? A sensitive project? I don't see a moral imperative for any of those to be free and open to all users.
Software licenses don't change ownership. That requires transfer of copyright, like with contributor agreements.
Though I am aware that a small set of people seek less copyleft licenses because they think they're better. They are usually wrong in their thinking, but they do exist.
I'm not sure what you are referring to about ontologically bad. Has someone said this?
I'm going by the vibe of the comments of people here who are generally anti-MIT. That the very nature of allowing someone to use your code in a closed-source project without attribution is bad. Phrasing it as "hiding their copyright infringement", for example, implies that it is copyright infringement per se regardless of the license or the spirit in which it was released.
Oh no I mean that there are companies that just don't care about licensing and plod ahead hoping it's never an issue. Like having devs build a "prototype" that they know uses AGPL code and saying, "we will swap this out later" and then 6 months later the "prototype" is in production.
Personally, I make a lot of my personal projects' code closed because I specifically don't want it to be useable by others. Not for jerky reasons, but strategic ones. IMO common licenses don't achieve what a lot of people hope they do.