Lol as we've discussed before, inaccurate but funny.
this post was submitted on 15 Jan 2026
476 points (87.5% liked)
Programmer Humor
28439 readers
2288 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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
From what I've heard about Windows, it works more like the Simpson's Barney coming up behind Moe meme.
So, as it should be.
While the meme is very funny, it is technically incorrect. Linux has two major ways of terminating a process. When Linux wants a process to terminate execution (for whatever reason) it first sends the SIGTERM signal to the process, which basically "asks" the process to terminate itself. This has the advantage, that the process gets the chance to save its state in a way, that the execution can continue at another time. If the process however ignores the SIGTERM signal at some point Linux will instead forcefully terminate the execution using the SIGKILL signal. This represents what the image shows.
Before someone gets mat at me: I know, that there are like 50 more Signals relevant to this, but wanted to keep it simple.
Simple answer for us simple folk. I like it. Thank you!
I think it is showing sigterm correctly. Sigkill wipes you from existence without leaving a body or trace of memory.
Does the "SIG" stands for "Signal"?
Special Interest Group. An internal committee convenes to decide the fate of the process.
(I don't know the answer, but I'm pretty sure it stands for signal.)
I like to secretly imagine it stands for SIG SAUER. Bang = process ded
Eh, it works more than 80% of the time.
The problem with Sig is they work too oftem, particularly when you don't want them to
80% of the time it works every time!
You're likely bumping into processes which are blocked by IO or are zombies.
load more comments
(1 replies)
Android/iOS users: What is “closing“? What is a „program“?
Android folks generally know because we have to close them sometimes. Don't know about iPhoners
Stop spreading this lie. Linux has a more graceful shutdown process than Windows ever did. It doesn't abruptly kill everything.
Unless you told him to do so. 🙃
Well, I don't know whether it's by default, but systemd does so - if the program doesn't close in a timely manner (or there is an exception configured)
Windows:
- program refuses to shutdown
- system: okay, guess you don't need your computer to turn off anyway
Such grace.
There is a windows registry hack to set the shutdown wait time for 1s and that did fix it for me. But every update they turn it back to unlimited.
(I ended up installing Linux, I only have the dnf5daemon server holding the shutdown up for atnost 5min now. But I haven't tried to fix it)
Which is why in my Windows days I got a habit of turning computer off with Windows + R --> shutdown -s -f -t 0
Windows just works, my ass :)
Windows task manager:
Let's play a whack a mole game where the app you're trying to kill constantly moves up and down a list by default! Enjoy!
There's a non-obvious freeze function in the Task Manager - for as long as you hold the Ctrl key, it'll stop updating the list. I have no idea why this functionality is hidden, but I guess Dave Plummer had some unusual ideas about UX.
load more comments
(1 replies)
Graceful like closing a laptop and putting it in a backpack only to have windows refuse to shutdown and become a heater until it cooks the battery and ruins the screen....
load more comments
(7 replies)
I mean, also look at how windows installs programs. Its like a 100 step process taking several minutes, because just putting the files where they need to be is just too simple.
Or the uninstall program, cant just remove the files, no... Need to run full installer backwards to remove all the registry entries and even reboot the system to get rid of it all.
"apt install " is just so much nicer than running some weird installer.
One of the actual (many) reasons that drove me from Windows. Over the years it became so dirty to have so many old files and registry entries that were abandoned by their respective uninstallers that I became wary of installing anything at all, and that's not the feeling I want with my personal computer.
Uninstallation on Linux needs to do the equivalent of removing registry entries (settings) as well. Neither prices typically takes long. Windows does require more reboots, but you can typically get away without rebooting still.
That's what --purge is for, in apt.
The main difference is Linux package managers with their package metadata is better at cleaning up than corresponding Windows installers.
Especially antivirus programs, they are the worst
Linux settings are stored in files in your home directory, and uninstalling typically leaves those files intact.
Some of them, but not all of them. Uninstalling things on windows also often leaves registry entries. It's just not that different
Why am I cross-posting .ml content?
I cross-post from .ml to the nearest relevant non-.ml comm to reduce the influence of .ml comms and indirectly, the instance as a whole, to make it an easier decision for other instance admins to defederate because one key reason I identified that admins don't want to defederate is because .ml still has some very large comms and some niche comms.
Some highlights from the link:
"Don't worry guys, the Uyghur Genocide was REALLY just birth control! ~dessalines, .ml admin, dev https://lemmy.world/post/30580167
"See! nobody died IN Tiananmen Square, just AROUND it, so it doesn't count!!" ~ Davel, .ml admin https://lemmy.world/post/30673342
.ml admin, Nutomics continued transphobia https://lemmy.world/post/29222558 The original transphobic Comment from Nutomic: https://lemmy.world/post/18236068
"NK is actually good and anything counter to that is Western propaganda!" ~dessalines, .ml admin, dev https://lemmy.world/post/31595035
General negative sentiment to other instances who haven't "seen the way" yet ~davel, .ml admin https://lemmy.world/post/27426510
"If you don't support Russia then you just don't understand geopolitics" ~dessalines, .ml admin, dev https://lemmy.world/post/27352415
And so so much documentation on clear heavy handed censorship and bias also on the link. So much I can't even put them all here because this comment would be really long.
I believe the behavior of its admins (the main admins are Lemmy devs) does harm to the overall growth of the Lemmy-verse and maybe even the Thrediverse (since Lemmy kinda kicked off the Thrediverse) because of its association with the devs of Lemmy and their insistence to use .ml as their personal political platform to spread harmful propaganda
On the outside, bringing up Lemmy frequently leads to comments like "Lemmy? Isn't that the place with a bunch of tankies?" Or "Tried Lemmy, but found it full of pro Russia crap so I left". The best way forward from that I see is to either widely defederate from .ml like the rest of the Triad, or pressure them to put a fair and unbiased as possible admin team.
Thank you for your service.
Ironically it's actually the opposite. Linux has signals, and with the exception of SIGKILL and I think SIGABRT they can all be handled gracefully. Windows on the other hand doesn't have signals, it can only TerminateProcess() which is forceful. The illusion of graceful termination on windows is done by sending a Window close message to all of the windows belonging to a given process, however in the event the process has no windows, only forceful termination is available due to the lack of a real mechanism to gracefully terminate processes. That's why the taskkill command tells you a process requires forceful termination when you run it against something headless.
You're right about Linux but you're wrong about windows. It is sent to the event loop in windows https://learn.microsoft.com/en-us/windows/win32/winmsg/window-notifications. It's been a long time since it was my job, but you actually had to pass a certification that your application exited gracefully in response to these messages as part of the partner program back in the day.
You clearly didn't read my message...I said a "window close message." I.e...WM_CLOSE. that is not a process signal, it's a window management signal. Hence taskkill not working without /f on headless processes
load more comments
(8 replies)
Windows: If you can't exit gracefully, I'll make sure you never exit at all
load more comments
(3 replies)
view more: next ›