@mholiv yes. Literally the reason why I use MIT licenses in my software. It’s possible for real people (same as me) doing real work to use my software legally and I don’t care if they hide their patches from me. I don’t really care about them at all - I just supply software as it is.
Then why not LGPL or MPL 2.0? They could use your code as is too. I’ve worked in major tech companies and they are ok with these. They just don’t like GPL for obvious reasons.
Obviously too is that you have the right to choose how to license your code, but I don’t think it makes sense to use MIT when LGPL and MPL 2.0:
Exist
Are accepted by tech corps for internal use.
If you don’t believe me look at your corps license inclusion policy.
@mholiv yes. Literally the reason why I use MIT licenses in my software. It’s possible for real people (same as me) doing real work to use my software legally and I don’t care if they hide their patches from me. I don’t really care about them at all - I just supply software as it is.
Then why not LGPL or MPL 2.0? They could use your code as is too. I’ve worked in major tech companies and they are ok with these. They just don’t like GPL for obvious reasons.
Obviously too is that you have the right to choose how to license your code, but I don’t think it makes sense to use MIT when LGPL and MPL 2.0:
If you don’t believe me look at your corps license inclusion policy.
@mholiv tried to look at MPL 2.0. Too long, didn’t read, lol. Maybe later I’ll look at it closely.
I will say shortness is a major advantage of the MIT license. Easy to understand.
For the MPL 2.0 here is a good short reference.
https://www.tldrlegal.com/license/mozilla-public-license-2-0-mpl-2