logoalt Hacker News

palata • yesterday at 8:04 PM • 1 reply • view on HN

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.


Replies

solatic • yesterday at 9:03 PM

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!

➕ show 1 reply