this post was submitted on 28 Aug 2023
676 points (91.5% liked)
Programmer Humor
32730 readers
85 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You still own the code you release under GPL. the restriction you are describing is actually caused by the non-copyleft licences you claim to prefer. If you choose to use MIT, you are limiting which libraries you can use. If you had picked GPL to begin with, you can use any library.
I don't exclusively own my own works anymore. Which is different than just owning your own work. Exclusivity allows you to sell something. Without that ability, you can't convert a product into money as easily.
If the exclusive ownership of something, in order to sell it, is the primary choice driving factor of a project. Then you should just make it proprietary. Anything else would limit your margins, since someone else can just fork your project, change it and make it proprietary themselves. A dual license is sometimes used in this case as well.
You can sell GPL licensed software. You don't have to publish the source code publicly online.