No, they're terrible. Windows can and does know when a system is least in use and is supposed to handle this during those periods. Updates are important but this is an excessive and unnecessary way to fix the issue of people not performing their own updates.
That looks like a conference room PC, I would doubt OP even has any control over that and possibly didn't even have access to the room until right before
It isn't their computer.
It's likely on a campus domain managed by campus IT and should be configured with a sane update policy that automatically does this overnight when the systems aren't being used.
I have no interest in giving them the benefit of any doubt, they not only haven't earned it but actively squandered and destroyed the trust they had earned in the past.
They'll actually have to do something to make themselves trustworthy again, and even if they do, there will always be the threat of them reverting to what they are now or worse looming over every good thing they do.
They not only became what they set out to oppose, they've become so much worse.
Add into that, I'm betting googie will actively try to make downstream forks difficult to maintain without accepting the components they want to force on everyone like manifest v3
I mean, sure, if that's what someone is saying, but I didn't see anyone suggest that here.
Companies violating regulations can be made to follow them without tearing down the company or product, and I'm absolutely not convinced LLMs have to violate the GDPR to exist.
Sounded more like enforcing the regulations without destroying the company or product to me, which I would have assumed was the preferred avenue with most regulations
Same, every new system that defaults to nano and throws me in here when I'm expecting vim I have to stop and remember what the characters mean right before changing it to use vim (like, seriously, I typed "visudo", not "nanosudo", why the hell would I expect it to open in anything other than vi or vim?)
By looking up the command. It took like two seconds and that was nearly twenty years ago. And I've been using it off and on since then (only off because I've not been consistently using Linux, not because I'm using a different terminal text editor; when on *NIX, vim/vi is pretty much all I've used on the terminal)
I've frequently seen Windows ignore that setting and force the restart while the system is actively being used
The mega corp neither needs or deserves your defense. They've fucked up the update system with Windows 10 and it's not gotten any better since then.