1002
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 16 Jun 2024
1002 points (88.6% liked)
linuxmemes
20363 readers
1539 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
My personal philosophy:
That's usually not what someone would want to do. The default if you don't provide a license is essentially "all rights reserved", and you're not granting anyone else permission to use it in any way. Everyone that wants to use it has to get explicit permission.
If you really want "no license" then you probably actually want to release it as public domain.
For truly small random pieces of code I'm putting online, yes, that is what I generally want. (Also, that's sort of presumptuous to believe you know what I want better than myself.) I'm not going to hunt down people who are infringing on projects like this: https://github.com/JacksonBailey/julian
I made that because I was bored and thought I could easily solve a problem my wife described having at work. If someone copies and pastes it into their own project do I care? I mean, sort of? Not really. It's just too small to worry about. Specifically leaving it unlicensed gives me.the freedom and flexibility to license it as I choose in the future and also pursue people using it if they refused to stop. (Although this example is particularly trivial. I probably wouldn't do that. But that's my whole point, I'm only choosing to do this with trivial code.) Applying a license doesn't give me that flexibility though.
(Apologies for typos, I just woke.uo.and don't have my glasses on either.)
It's more that people won't use the code at all if there's no license attached. For someone that's looking for a snippet of code to reuse, it's much easier to instead find a permissively licensed piece of code that performs a similar function, instead of contacting the author of the unlicensed code and trying to figure out what to do.
Sorry - I meant to address it to readers of your comment rather than you. I edited the comment to make it clearer.
I think you're putting a lot of faith in people when you say that. When's the last time you properly obeyed a license when copyijg and pasting from Stack Overflow? When's the last time you think the average dev did?
Also, no hard feelings about the presumptuous thing. Idk why I got defensive.
And as an aside, I think I've heard that in some jurisdictions there is no concept of public domain and in others you cannot willfully put things into it. So licenses like CC0 or the awfully named Unlicense are better alternatives. (Bad name because Unlicense and Unlicensed are so close in spelling but wildly different.)