this post was submitted on 22 Jun 2023
35 points (92.7% liked)

Programmer Humor

19594 readers
831 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] JackbyDev@programming.dev 0 points 1 year ago (2 children)

Because there are words that have less violent associations that can still capture the relationship sought to be described.

[Stop using Nazi, war]

Those aren't used for computing though. And, yeah, I think if we did we probably should. Like if terms related to genocide were used for stopping a lot of processes at once that would be pretty weird to me.

[death]

Kill is used to refer to stopping processes and that's probably where the line is in my opinion. It feels very different to me to say "kill a process" versus "genocide a group of processes"

[–] lowleveldata@programming.dev 5 points 1 year ago (2 children)

We do use war. It's a common package in Java. Should we rename that because it might make people uncomfortable when we say "We are going to deploy the war tomorrow"? Why can't we just accept the fact that words have multiple meanings?

[–] Hupf@feddit.de 6 points 1 year ago (1 children)

I want to update the web app but war never changes.

[–] lowleveldata@programming.dev 6 points 1 year ago

hmm... have you tried nuking everything? That might help

[–] JackbyDev@programming.dev 1 points 1 year ago

No, because it is an abbreviation for web archive.

[–] FaceDeer@kbin.social 2 points 1 year ago

There's a project I'm following where an opcode called "SUICIDE" (which deleted the program it was triggered from) was renamed "SELFDESTRUCT" because people were bothered by the reference to self-harm. I personally considered it a waste of effort, but at least in that case it was really just a matter of changing some strings in the documentation and having compilers accept either label for it, since the opcode itself didn't change is value.

The opcode is likely to be entirely deprecated soon anyway, which IMO makes it even more of a waste of time. Oh well.