this post was submitted on 12 Apr 2025
123 points (94.2% liked)
Asklemmy
47431 readers
1927 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
@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