| > those in countries like Germany where you're not allowed to dedicate works to the public domain That sounds like Germany's problem. If the system makes it difficult for someone to accept a gift of code from me, is it up to me to fight or work around that system? No matter what license you pick, in all likelihood some territory somewhere will have a problem with it. > many companies don't allow you to use code with the unlicense because of its unclear legal status Again, if I particularly care whether commercial entities use my stuff or not then I probably care about licensing enough to not use this the unlicense anyway. They can always contact me to negotiate specific commercial licensing for their use case. -- There are to (at least) views that head in this direction: * I don't care about licensing: I want people to use this, and I don't care how. * I don't care about licensing: I don't care how people use this, I don't even care if you don't use it at all. The one thing you should take care about, even if you don't otherwise care at all, is that some licences contain accidental traps which potentially enable legal grifters to bully people who use your stuff. The most obvious case of this is version 2 of creative commons licences (newer revisions are not prone to this, v4 (released in 2013) certainly, I've not looked to see how v3 (2007) stands in this regard), see https://doctorow.medium.com/a-bug-in-early-creative-commons-... amongst other places for details. |
If you want to make a gift, it's up to you to do it the right way / to allow people to get it, don't you think? You already put some effort to build and wrap it, you could as well stick some small label on it (put some working license), that's quite easy to do in comparison.
The rest of your comment hints at why you should pick a recognized license in any case.