They can try to extinguish over my dead body.

They have no packages but do a full patch of the system data. Since this is the most complex approach and almost everything can go wrong down to the core they spend most of the time with checking and cleaning state.

This is a byproduct of one of the largest and more ignored differences between windows and linux. The fact that Linux let’s you modify files while they are open whereas windows doesn’t.

This means that you can update a linux system by just replacing the files with the new ones while it runs. On the other side, Windows can’t modify its own files while it runs, so instead it has a second entire OS to update itself, and requires a reboot to unload all the files and boot from the updater without locking windows files.

Can’t remember a windows update taking longer than 5 minutes. And even if it did take that long, you can just press “update and shutdown” when you stop using the pc. Windows has a lot of problems but this isn’t one of them.

The Nintendo Switch is the gold standard of updates for me.

and on linux you can upgrade while the system is running and then reboot

Lack of proper package management is my assumption.

Mac updates are less frequent but take longer. They also restart the machine. One difference though is that my mac never took it upon itself to start an update without asking my opinion.

I hear it takes a long time on Macs too!

thankfully I don’t have this problem on my Gentoo

WSL exists on a Windows system which means you’re still subject to Microsoft’s rather insane update practices.

Should have laughed if this was a corporate device. They ignored the continuous popups for too long and was forced into compliance at an inconvenient time because they couldn’t be bothered to reboot at the end of the day for likely 2 weeks.

Back when Microsoft started showing interest in and contributing to Linux, I knew that they were up to something no good like this. But honestly, anyone who thinks that WSL running inside a very abusive Windows environment is an alternative to true Linux/BSD experience, is frankly clueless. They deserve everything MS subjects them to.

Why? What’s wrong with WSL?

Well yeah, stable running on unstable is still unstable. Cant’t build a fundament on sand. etc.

Everything that doesn’t involve Microsoft is more stable.

Last week an update broke my moms mandatory TPM nonsense module thingy. Like bro, this is a laptop that ships with win11 preinstalled and an update breaks your preconfigured system? I can’t even comprehend. Like how the heck are casual users supposed to deal with that?

Well there’s msys64/mingw for clang/gcc anyway. Fuck VS.

That would require Microsoft admitting they come in second.

It actually makes sense. It’s a subsystem in Windows (therefore a windows subsystem) that makes Linux work

From where do you think comes the Balmer peak?

https://xkcd.com/323/

Microsoft has always been terrible at naming things. And at developing things. And at literally everything.

It is a subsystem of Windows that Linux runs in. It’s not a subsystem of Linux.

Windows is the system. It’s the host operating system. It created a subsystem specifically for running a child operating system. In this case, Linux

In what world would Microsoft allow the Linux name to appear before Windows? If MS were a person, they would be diagnosed with Narcissistic Personality Disorder.

It’s also usually lawyers that create these names. I worked on databases for IBM Cloud and they were all called “IBM Cloud Databases for Elasticsearch” and what have you. Despite it being an offering of the database on IBM’s cloud.

Since Elasticsearch is a brand name, the “host” corporation corporation has to present it as a product “for” the brand name rather than as the brand name itself to avoid implying that they are acting AS Linux or Elasticsearch or whoever is the third party.

That must have been an incredibly shitty virus scanner if it complains about Windows features.

The VPN client I’m using doesn’t play properly with wsl, so I can often randomly not use internal services, because there’s no route available. Unfortunately, that includes our k8s cluster, so I have to use a different kubectl outside of wsl to work with it. Awesome.

As a software developer, I still struggle with windows fuckery. I have to manage about a dozen machines, each of which has different tasks, and sometimes they decide to just up and reboot for the mandatory update. While I am out of state.

Uhg. I spent time yesterday writing a windows service to perpetually send a WoL magic packet to those computers just to avoid this situation again. They may never shut off again.

I mean… There’s videos of it suddenly doing an update in the middle of people’s gaming/work sessions lol. I used to stream way back when windows updates were at their troll peak and had one kick off in the middle of a stream. It just happened randomly to some of us regardless of what was scheduled. I don’t imagine it happened more than once for too many people. Generally speaking it’s pretty good about sneaking updates in even though I detest how aggressive it is about them

There’s always the centrally managed corporate Windows desktops. My workplace is better about this now, but previously they’d just push down updates and with some of them you’d have little other choice but to let it proceed no matter how inconvenient the timing.