Scoopta

Honestly I feel like that's very common with Linux. If you're willing to deal with the growing pain of switching it ends up working out better in the end, some people just don't want to deal with that or it's their job and they can't afford to deal with that. I'm sympathetic to the latter case, less to the former but that's just my opinion

It's gotten better but I'm not v6 only, I just don't have v4. I have NAT64 which basically uses your IPv6 as the private address in a traditional NAT setup, allowing you to continue to access the legacy internet without IPv4 inside your network. Catch is you can't connect to IPv4 addresses because it relies on a DNS64 server to generate IPv6 AAAA records from the IPv4 address when a domain only returns IPv4 so only DNS based services work. Basically it lets you have all the befits of a v6 only network with few of the drawbacks.

...right...I can't view this meme LMAO...I don't have IPv4 on my network 🤣

Too bad it doesn't work, probably because of vhosting

Yep, I'm aware of that too, doesn't change my initial point

...right...tell that to cmd.exe or the OpenVPN daemon, or the soft ether VPN daemon, or OpenConsole.exe, or Idk, I only tested 4 that immediately came to mind but my point stands. There are a lot of programs that do not have a window handle and do not bother with window messages.

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

TIL about the console signaling stuff, good to know. I am aware of SEH but that seemed a little too in the weeds for this discussion since that's as you say akin to SIGSEGV

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.

This isn't exactly true. UEFI supports arm and if I'm not mistaken windows on arm is UEFI only. While UEFI isn't as standard as it is in the PC world it is very common on servers and windows devices.

LMAO no it's not lol. It's figure fantasy (it's unavailable in NA at this point. Only SEA and EU)

I have one, it's a gacha game my co-worker got me on years ago and I haven't broken the habit