what license should i use for my lexer generator (and future parser generator maybe?)
i'm not really interested in "ethical source" licenses, as i believe we can't use copyright effectively in that way. but of course i will have a coc and contribution policy banning problematic shit like genai, fascism, transphobia, ableism, racism, etc
1 Boost
0 Likes
@lumi regarding copyleft compatibility, EUPL allows most compatible afaik. it's why i started using it at some point. but now i'm not sure if i really want to keep it bc the license is "or later" by its own terms and i don't trust the eu to not suddenly sneak in some ai exemptions or whatever 😐
@ilja@ilja.space i didn't know that .. that is kinda ick
i also do not trust the EU at all
@lumi sadly, copyleft is still copyright, so i prefer public domain licenses (or something like cc0 or the unlicense). it can probably be argued that copyleft is a sort of self defense, but sadly it's non-specific and hits everyone.
@lain @lumi Personally my go-to usually is 0BSD. Unless there is a risk of some malicious takeover of the codebase, in which case (A)GPL is justifiable. I would even go as far as modifying the Sybase Open Watcom license to be universal, since it makes takeover nearly impossible (and makes GNU/People mad).
@lumi AGPL, it makes HN temporarily embarrassed billionaires melt like the Nazi opening the Ark
i personally just don't care that much about licenses anymore. i hate proprietary software and believe it should not exist, of course
but copyleft can be useful to at least send a signal, though it also reduces license compatibility
i wish copyright just didn't exist. it's a horrible and abusive thing
and software freedom should be put into law: if you distribute any program then you have to distribute the inputs used for the build of that program, in the form that the dev uses/used to actually develop it. so that the user can always build a bit-for-bit exact copy of the whole program (binary + all other resources)
anyway. that was my rant. lmao