According to RMS, adding usage restrictions to an open source lucense is not a very effective at stopping the software from being used for evil but is a huge headache for a FOSS ecosystem (because it adds to the number of subtly incompatible licenses that we need to work around)
And I'll clarify, in today's world code has severe moral repercussions, especially in the fields of AI and vision. Why shouldn't we have more discussions over ways that we can add caveats and nuances to the licenses in order to distance our consciences from repercussions.
We should, but this isn't the right way to have the discussion IMO. As OP noted, this is impossible to enforce, so it's more symbolic than anything. Which is fine, but it comes with the cost that anyone in a company that observes OSS licenses will need to decide whether it's worth having legal sign off on it, even if they aren't involved with a military (since it doesn't fit under a pre-approved license). This applies not only to OP's code, but any code that uses it as well, so even if OP decides this cost is worth it other non-military users may avoid the code anyway.
Comments
Why should the open source philosophy trump any other moral objections?
According to RMS, adding usage restrictions to an open source lucense is not a very effective at stopping the software from being used for evil but is a huge headache for a FOSS ecosystem (because it adds to the number of subtly incompatible licenses that we need to work around)
https://www.gnu.org/philosophy/programs-must-not-limit-freed...
And I'll clarify, in today's world code has severe moral repercussions, especially in the fields of AI and vision. Why shouldn't we have more discussions over ways that we can add caveats and nuances to the licenses in order to distance our consciences from repercussions.
We should, but this isn't the right way to have the discussion IMO. As OP noted, this is impossible to enforce, so it's more symbolic than anything. Which is fine, but it comes with the cost that anyone in a company that observes OSS licenses will need to decide whether it's worth having legal sign off on it, even if they aren't involved with a military (since it doesn't fit under a pre-approved license). This applies not only to OP's code, but any code that uses it as well, so even if OP decides this cost is worth it other non-military users may avoid the code anyway.
Have all of the discussions about that you want, just don't pretend that what software you release is open source if it in reality is not.