36
Should I choose MIT or BSD 3-Clause for my engine?
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 15 Jul 2026
36 points (100.0% liked)
Open Source
47928 readers
253 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 7 years ago
MODERATORS
I thought of using GPL, but it would mean someone else would be obliged to open their source code if they base their software on my engine. Though open-source is good and must exist (speaking of Ren'Py, which is not GPL, but still an open-source engine considered a golden standard of VN development), I'd like to give others the right to make their derivative works either open or closed, by their choice.
As for AGPL, I know nothing, unfortunately.
That's understandable, though one of the other commenters suggested the LGPL which might make for a good fit for your case. Here's a comparison with the other two if you're interested.
The AGPL is just the GPL with extra rules requiring sharing the code even if you expose it exclusively via a service.
Okay, thanks for the advice. LGPL might be a good option, I'll look into it.
See my other comment: https://programming.dev/post/53544261/24909721
AGPL is GPL + network services protection (preventing someone taking your code and spinning up a for-profit selling services without contribution back). If you don't care about people stealing your code, closing it, and selling services based on it, then there is no need to consider strict copyleft licenses.
Okay, thank you very much. As for now, I hope my engine will be known enough for anyone to recognise the hoax.
Do you know that Apple's macOS is historically a FreeBSD fork? (They have copied big parts.)
I find it notable that FreeBSD is struggling to stay alive, and Apple's 1000000000000s of dollars in incomes does not help them at all.
Huh, lol. No, I didn't know that. One of my friends uses FreeBSD, and he likes it. But yeah, that's a good point.