I know that many people would disagree with me on this, but thankfully I'm free to choose what license I consider "free".
Then you shouldn't release it under the MIT license, which has restrictions and requirements on speech. You have to release it to the public domain. Pretending MIT doesn't dictate terms under which you can release your own software is just a fantasy.
But please don't forget about the users. Only the copyleft licenses guarantee (legally) that the user gets to enjoy the freedoms, too.
MPLv2 is copyleft, but not "viral": so you can use an MPLv2 dependency just like if it was MIT, but if you modify it, you have to distribute the changes.
Especially in a modern day and age where agents are more powerful when they can quickly privately vendor a dependency, patch it, and move on, with zero political ceremony or fuss, MPLv2 feels like an anachronism.
> except if they want to benefit from patching code they didn't write without contributing back. But I don't think we should encourage that.
The spirit of free, open-source software is that you are free to do as you like with the software, no matter who you are. It somewhat boggles my mind that people will hold up licenses like GPL that do not forbid military use, it's totally fine if you deploy GPL software in war, because we wouldn't dare tell you what you may or may not do with the software.... unless you want to make changes to the software, in which case, see you in court!
If you don't modify it, it behaves exactly like MIT. If you want to modify it but not maintain a fork, you can contribute upstream. Or you distribute the sources, which does not require a public repository.
But mostly, why would I care about companies making profit by using my code privately? As an individual, what I care about is being able to fix the devices I own. And copyleft helps with that.
> unless you want to make changes to the software, in which case, see you in court!
Right. So you don't really understand how GPL works, do you? GPL requires you to distribute the sources to the users. It does NOT, at all, require you to make the changes publicly available. So GPL works really well for the military: if you sell a product to the military that contains GPL code, you just have to distribute the sources to them. It's actually better for the military as well! It's better for all the users.
Also you can not mix propriety code that you don't own with GPL which is also a showstopper in many cases.
Yes that's correct. Which makes GPL viral, but not MPLv2. My point was that while I understand how GPL may be too much for companies, I don't think MPLv2 would be.
I have been in big companies that were fine with using (properly) LGPL and MPLv2, by the way.
> Also you can not mix propriety code that you don't own with GPL which is also a showstopper in many cases.
I am not sure I understand that. You can mix proprietary code with GPL, the licence has nothing against that. What you cannot do, though, is distribute proprietary code you don't own and don't have a right to distribute. But that's independent from GPL.
Say you use some software to provide data you host to end-users. Say that software relies on some system package or architecture that isn't available on your server, so you make minor changes and rebuild it to run.
Now if you wanted to make a proper change to the software to accommodate different target architectures/packages, you'd do things very differently; you'd write some check and delegate to the provided apis based on that.
But you didn't do that, you did a find and replace.
This has no value to anyone else, and it also reveals internal information about your system that you may not want to reveal.
This conversation has come up a lot, and I’m always amazed at how hard it is for people to accept that maybe the MIT license (and other permissive license) people actually want the MIT license terms and there’s no more complex reason behind it.
I’ve read so many rationalizations that frame it like GPL was the default or right choice and then something happened that made people defect away from it. Blaming RMS is common.
I think the more honest read is that people and groups decided that MIT matched their goals and decided to use it. Not that they defaulted to GPL and then found reasons to leave it.
Does the same thing apply to Mickey Mouse? Would you say it's fine to use Disney characters in my own creations, as long as I take ownership of the outcome and put my money on the line for product decisions?
My point is that devs have always learned from open-source code and the internet, then used that knowledge to write their own proprietary software. Why should it be any different when AI learns from the same sources and produces new code?
Now just because same devs use AI to create code doesn't mean they should be banned from creating or owning a proprietary software.
The LLMs don‘t really reverse software though, instead they have gotten good at driving Ghidra and other tools, which has the same effect.
In fact, current US law says AI output cannot be copyrighted.
Open source code: reproducing and publishing the code without following the license is a copyright violation. Instruction a computer programme to do the same thing should still be a copyright violation. Since this is the internet, I need to state the obvious: trivial code (defined on a case-by-case basis) is not copyrighted.
Books: the author expects you to reproduce their work, as long as it’s not another book. You wouldn’t get many sales if you sued someone for using the things you taught them.
The internet: actually the same as open source code. StackOverflow enforces a specific licensing clause to allow people to use code you provide. People who write posts that say “use this code to fix this problem,” are implicitly providing a license, too.
I don’t think using an LLM to generate code should remove its copyright but it also doesn’t remove the responsibility to not violate copyright.
Same with the ecosystem of creative work. Will some humans be inspired by my code or other artifacts? Sure. Does it mean it's fine to introduce an automated 1000 times more effective plagiarism machine to that ecosystem? Probably not. Certainly not if avoiding destroying the ecosystem is your consideration.
By this logic, shouldn't any code using a copyleft framework or language also be copyleft?
and yes duh
No, that's not how copyright works.
And I won't comment the rest.
You're confusing writing code with software engineering. Devs never just wrote code, they took ownership of the outcome. Business owners put their money on the line for product decisions.
To say that just because devs or founders use AI to write code, the code is no longer their intellectual property is ridiculous. Humans take responsibility for the outcome and are willing to accept the losses. AI can't do that. AI doesn't have any stakes in the output it generates, humans do.