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