Crockford on JSON license (2011)
While this is funny, it does highlight that you should probably have an actual legal opinion if you decide to write your own license. A less tongue-in-cheek example that I've run into is <a href="https://dst.lbl.gov/ACSSoftware/colt/license.html" rel="nofollow noreferrer">https://dst.lbl.gov/ACSSoftware/colt/license.html</a>. "any usage related to military applications is expressly forbidden", which is still poorly defined enough that it makes lots of corporate lawyers nervous and you end up having to remove those packages even for stuff that isn't really a military application just because it's not clear how military-adjacent something is allowed to be. It's especially ironic since it's being distributed by a Department of Energy national lab. I wonder if DOE national labs ever have military applications...<p>It's also not clear to me that this does actually make it illegal for the military to just use it directly, even if they cared about following the letter of the law. If copyright is the real power behind the enforcement of open-source licenses, I'm not sure usage is something the license grantor gets to dictate as long as you're not redistributing something.