My favourite kind of updates are those that happen on a Friday afternoon where you push all the buttons you think you have to, and it looks like it's getting on with it, so you switch the monitor off and go home for the weekend, then when you come back in on Monday there's another popup that says "you have to push this button for no reason before I'll install these updates" and then you have to sit there watching it update because it's sat there for the entire fucking weekend waiting for you to push that stupid pointless button.
I wish there was a checkbox that says "Complete updates without requiring any further user input. Wanna reboot? Reboot. Wanna download some shit? Download some shit. Wanna start installing some shit? Install some shit. Wanna repeat over and over? Repeat over and over" or something like that.
That last paragraph.... WINBLOWS ALREADY DOES THIS!
i swear it does it when it's not supposed to. In the past 6 months my desktop has been waking up from sleep, and also me, just to start an update I was even unaware was happening. And if it's not updating the system it sits there at the login screen.
So I've started shutting my pc down before bed to avoid this happening.
Edit: not the checkbox thing. It updates and downloads stuff sometimes without me telling it to.
Windows updates always release on the second Tuesday of every month. They have been doing that for 20 years or so. How does anyone get surprised by them?
The only out of line updates are critical security fixes for actively exploited issues and those are rare.
It’s not the surprise. It’s the soul crushing, unavoidable inconvenience of never having any say as ads get forced, new unwanted features get added, more AI bullshit injected, more updates now, no matter what you have going on… for all time.
It’s the fact that there is no choice for users but to just accept that Microsoft is forcing them to turn the computer they had last year into a totally different computer this year.
I had Windows force a reboot and I could not do anything about it. And in multiple cases it did not let me to shut down my laptop without installing updates. It's really fun when you're in a rush and have to leave and take your laptop with you, but Microshit does not let you shutdown your fucking PC without doing updates for the next 15-20 minutes :)
First of I run linux on my personal machine.
Second, I shut down my work machine at the end of the day and if there is an update - let it update. The result? Not a single problem with windows updates in years! Strange, I know.
Sidenote: I always thought people were partially making fun of windows updates because you have to reboot all the time. I have to log out to switch from integrated to dedicated graphics in Linux and pretty much 90% of all updates require a reboot. And to conserve battery I have to shut down the laptop anyway, since hibernation is but a dream. But whatever, it's not a competition.
When you have a nice setup in programming (compiler, database, diverse docs, shells etc), you don't want to shut all that down. If you can, good for you!
My dev VM is almost entirely disposable. Could be up and running again, fresh in 30-60min, not counting time to pull the repo. Why use a local db server? Seems weird to me but, I came to development through SysAdmin and support stuff, so, was used to not owning the machine that I was on. That probably has heavily influenced my workflow.
Out of curiosity, would you mind sharing a bit any the languages/frameworks and workflows that you are using? I'm mainly using Go, C++, Python, and a few others and just having trouble figuring out how I'd arrive at a situation like that. No CI/CD and test systems?
Well if I shut down visual studio, it takes some time to relaunch it, it uses a distant unix server to compile.
I usually have a bunch of explorers open on distant repos for checking traces. Some soft connected to a database (with tables open), shells open on servers, or inside a docker on that server, all that goes away at reboot.
Nothing crazy, it's just convenient to just continue working instead of having to set it all up in the morning.
CI/CD, thats for integration and should IMO be on a server somewhere 😁 not on your PC that you shut off in the evening!
I do mostly C/C++, linux/windows. Database, gui, etc.
Windows Update is just dogslow and forces a reboot. For me even a significant distro update takes much less time and it doesn't force you to reboot (nor to update for that matter).
I don't have to reboot after an update very often, almost never really. It's kernel updates where I have to reboot, other stuff I can restart and avoid it that way if I still want to keep the pc on.
I know on some systems hibernation (suspend-to-disk) can be fiddly. For me it worked out of the box which was nice.
All of our laptops are either Mac or Linux. Eight or ten years ago it was all Mac but now it's mostly Linux. Ultimately, clients that have closed Windows ecosystems always provide us with laptops or a jump station to connect to. So if they are going to do that anyway, there was no need for us to Windows internally.
Absolutely. Enterprise license and MSDN was expensive and a pain in the ass. Once we dropped support for Microsoft as a whole and transitioned to Google Apps (early adopters) everything became easy. OSX never broke, although the hardware could be problematic at times. The main reason most of us started transitioning to Linux from Mac was Apple's hardware choices. That said, I have a MBP M3 Max for music and graphics and that Apple silicone is absolutely beastly.
Maybe hardware requirements have been met nowadays with even basic hardware (gaming excepted), I have a quad core linux and my SO has an old quad core mac, no real need to upgrade those. My brand new thinkpad for work is running windows, well not actually running, merely walking IMO, everything has to be scanned and uploaded, there are moments the whole PC freezes up for 30-40 seconds to check if you should be able to launch that same app again ...
That sounds like a dream. I use an MBP for work because the alternative is Windows. It really just ends up being a glorified ssh terminal to get to my Linux VM. I felt bad enough at one point that I switched to kitty to make better use of the M2 capabilities.
I work from home using a work provided laptop. One day my partner at the time was working on setting up a Kali machine, and every time they connected to the network my work laptop would cease all network communication. Guess whatever security software/settings my work laptop had was made very nervous by a Kali machine on the same network.
