Hacker News new | past | comments | ask | show | jobs | submit
A fair number of FOSS licenses were interpreted this way. The popular migration away from GPLv3 (might’ve been v4?) towards MIT, LGPL, etc had more than one cause (a huge one was the rapid sectoral commercialization; the decline of RMS’s reputation may have contributed, etc), but a big one was the potential interpretation of new GPL as being overly viral and “license-infecting” only slightly related software assets rather than wholly derivative ones.
> towards MIT, LGPL, etc had more than one cause (a huge one was the rapid sectoral commercialization; the decline of RMS’s reputation may have contributed, etc)

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.

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".

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.

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.

I genuinely don't see why anyone would need to be more permissive than MPLv2, 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.

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!

> 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.

loading story #50511667
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.
> 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.