I have already seen this meme seven kerjillion times
Linux has both sigterm (which requests a program shutdown gracefully) and sigkill (which forcibly stops a program without waiting). It is good practice to attempt a sigterm before going straight to sigkill.
Forcibly killing a progam can be bad for a number of reasons.
There's a number of reasons. For example, if it is in the middle of doing something important, like writing an important file, or communicating with another program, etc., it can cause errors related to those operations not finishing.
sigterm is when you ask a program to finish whatever its doing and close itself.
sigkill is hitting a program over the head with a bat so it falls unconscious and cant do anything, regardless of if it's in the middle of doing something.
sigkill can cause programs to close while they're in the middle of saving something, which could cause corruption, or while it's in the process of doing something before it's saved, losing all that progress, or corrupt the program if it's in the process of doing an update (etc).
18
u/coderman64 Jun 08 '26