-
Linux normally does a nice shutdown as well, unless you force it.
-
You can force it on windows if you really want.
I’m so tired of linux memes posted/made by people who don’t know much about windows or linux.
Oh, p-lease, can force it my ass, Linux has never failed to shutdown on me when using plain obvious GUI method. windows - can easily hang on forever as long as computer stays powered. The point of all the memes is exactly insane windows defaults, not the things that can or can’t be done by someone with enough knowledge
Windows also has to worry about getting sued by another multinational conglomerate when some idiot loses the only copy if a super critical file because they were too lazy to save and forced their laptop to shutdown so they could pickup lunch.
-
Linux programs either HAVE to be quick while receiving shutdown signal, otherwise the state will be fucked, work will be lost, and people will be mad, and program will stop being used.
-
Clicking the Windows button to force shutdown will straight up kill the program and won’t care at all.
-
-
Windows: Has a complex and graceful shutdown process to make sure programs never close if there’s a problem with them and your computer just stalls on shutdown until you hold down the power button and completely void out the purpose of the graceful shutdown.
Ever tell a pc to shut down and come after work and it’s still waiting for click a box.
Ever? Too many times. When I think I’ve told Windows Update “yes, do all the shit, yes it’s fine, yes I’m sure, yes you can do it, yes I really want you to do it, yes I’m sure I really want you to, yes I’m sure I’m sure, yes for the umpteenth fucking time” and switched off my monitor to go home for the weekend, the number of times I’ve come in on a Monday morning just to find I have to click “yes” yet again then have to sit there watching it grind out its updates.
I just wish they’d add a checkbox, off by default, that says “yes you can do it all, just stop asking stupid fucking questions” that I can click and go home. But for some reason Microwank insist I have to sit there watching that fucking update percentage creep up then endlessly sit at “100% all is done, please wait” for no reason whatsoever.
Oh yeah and there always seem to be way more reboots needed when BitLocker is active. I’m sure 1 reboot is the norm with occasional 2’s. But with BL it’s usually 5-6 reboots.
I used to work at a place where MS would raise tickets with us and I always wanted to give them the WU treatment. But professionalism always got in the way of “This ticket is 100% complete, you must close and reopen it to continue”.
Linux gives processes a chance to gracefully close. However, it also will absolutely NOT allow a process to hang up the shutdown or restart procedure after a point. If you’re using systemd (which there is a good chance you are), it’ll count down. If the process hasn’t stopped in the time allotted, it gets Old Yellered.
I’ve never seen anything graceful in windows
“Mmm, that didn’t work, try again later I guess? Just stop bothering me with your petty needs and get back to generating monetizable data that I can harvest.”
Closing correctly means the program stops NOW
kill commands make one feel like a Caesar
et tu, Sudo?
If your code can’t handle a sig9 then your code is weak
Close correctly my ass, window’s priority is to piss us off.
Except Windows doesn’t. You can send WM_CLOSE, but that may not actually bail out of the core loop. PostQuitMessage() works better for some apps, but not at all for windowless CONSOLE subsystem processes. Windows also has a lot of special behavior around generating signals in other processes. It’s a mess.
Like, every time I reboot the reboot UI complains about mysterious, unnamed processes that take suspiciously long to quit.
Having the kernel yank the process out of existence with prejudice is definitely the way to go as apps should be hardened for crashing, anyway.
sudo reboot, that way the gui gets to die in a fire, too!
Nothing is graceful about Windows. [=
Kill commands make me look like a CS:Go Civilian
You literally kill/xkill/killall the program.
In As400, you type PWRDWNSYS *IMMED.
Then you pray it comes back up in a timely manner.
Laughs in Sierra
elaborate please
old sierra DOS games, uh, they fucked up the code when exiting so they’d just crash. so they changed the error code to say “thanks for playing Kings Quest” or something similiar
Except when you install ESET EFS… may the guru save your source…