this post was submitted on 15 Jul 2026
33 points (94.6% liked)

Open Source

48852 readers
1177 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 7 years ago
MODERATORS
 

Hello everyone.

I'm developing an open-source visual novel engine. And I'm struggling to choose between the two licenses: MIT and BSD 3-Clause. I wasn't much about licenses until this moment, so I have to ask someone else. Which one should I pick and why, if someone knows?

Thank you in advance.

you are viewing a single comment's thread
view the rest of the comments
[–] somegeek@programming.dev 28 points 1 month ago (16 children)

Permissive license is basically for you and contributors to provide free labour and when mature enough, big corp X can just exploit it and use it for their own benefit off your free labour if needed.

There are actual good and big projects that use permissive licensing that have not been overtaken (postgres for example) but they mostly have very strong, cohesive business and market plan to achieve that, plus the bature of their software.

If your software is actually complicated and useful, don't let corporations exploit it for nothing.

[–] ArsFireside@lemmy.dbzer0.com 10 points 1 month ago (15 children)

Okay, so it's a threat if I use a permissive license. Thank you very much! I'll think about it.

[–] vas@lemmy.ml 2 points 1 month ago (3 children)

Or from the other side, GPL would guarantee that you yourself (and your project's contributors) would still have access even if a good fork emerges.

Things happen over years or decades.

[–] ArsFireside@lemmy.dbzer0.com 1 points 1 month ago (1 children)

Do you mean that without GPL my access to my own project can vanish?

[–] vas@lemmy.ml 3 points 1 month ago (1 children)

Your access to a popular and commercial fork might be non-existent. You would maybe not even mind that they're selling your code - possibly just wanting to tune it a bit, since you know how it used to work. But the fork can decide they're proprietary and they won't give you any source code.

[–] ArsFireside@lemmy.dbzer0.com 1 points 1 month ago

Aah, okay then. Well, it does make sense indeed.

load more comments (1 replies)
load more comments (12 replies)
load more comments (12 replies)