News for hackers. Stuff that matters.
Re:All AI-generated code should be Open Source by adwn on Sunday November 15, 2026 @11:16AM (#50508081)
For me, it's the latter: the GPL feels overbearing and patronizing, and I don't want some dependency to dictate under which terms I can release my own software. I pay the community back by using MIT whenever I open-source something. This feels more "free" than RMS's view of freedom.

I know that many people would disagree with me on this, but thankfully I'm free to choose what license I consider "free".

Re:All AI-generated code should be Open Source by jasonlotito on Sunday November 15, 2026 @02:06PM (#50509666)
> I don't want some dependency to dictate under which terms I can release my own software.

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.

Re:All AI-generated code should be Open Source by maxhille on Sunday November 15, 2026 @02:11PM (#50509724)
From the developer's perspective the difference between those licenses isn't that big when you open source your stuff anyway.

But please don't forget about the users. Only the copyleft licenses guarantee (legally) that the user gets to enjoy the freedoms, too.

Re:All AI-generated code should be Open Source by corysama on Sunday November 15, 2026 @02:22PM (#50509803)
RMS’s view of freedom is that devs should restrict themselves for the sake of the freedom of the users. AFAIK, that’s the explicit goal of the GPL.
Re:All AI-generated code should be Open Source by coldstreamflowi on Sunday November 15, 2026 @08:15PM (#50512830)
Yep, power for the masses not the few.
Re:All AI-generated code should be Open Source by palata on Sunday November 15, 2026 @03:04PM (#50510166)
Genuinely interested: why MIT and not, e.g. MPLv2?

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.

Re:All AI-generated code should be Open Source by solatic on Sunday November 15, 2026 @04:03PM (#50510729)
MPLv2 effectively prevents large companies from vendoring dependencies, since if you privately patch the vendored MPLv2 dependency, you are no longer compliant. Instead the large company would need to have an open-source fork of the MPLv2 dependency, with the patches applied in the open. In many large companies, getting any kind of public repository is practically impossible, so MPLv2 is unusable in those places.

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!

Re:All AI-generated code should be Open Source by palata on Sunday November 15, 2026 @04:53PM (#50511230)
> In many large companies, getting any kind of public repository is practically impossible, so MPLv2 is unusable in those places.

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.

Re:All AI-generated code should be Open Source by stateoff on Sunday November 15, 2026 @05:43PM (#50511667)
However: from my understanding the users are free to publish the source code and any NDA that would prevent this is not compatible with GPL. Probably not an issue with the military but may still affect the businesses that write the code.

Also you can not mix propriety code that you don't own with GPL which is also a showstopper in many cases.

Re:All AI-generated code should be Open Source by palata on Sunday November 15, 2026 @07:09PM (#50512345)
> from my understanding the users are free to publish the source code

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.

Re:All AI-generated code should be Open Source by pcthrowaway on Monday November 16, 2026 @12:03AM (#50514242)
I'll argue the case for permissive code not requiring users to redistribute changes.

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.