|
|
|
|
|
by kg
307 days ago
|
|
Windows ends up being a thousand cuts situation when you have enough software like this installed. If you want a responsive and stable system you end up spending a good amount of time troubleshooting freezes or mystery CPU/disk usage. As of yesterday (this started suddenly) any time Backblaze is performing a backup my whole system gets bogged down for no reason. Was fine days ago, so who knows what automatic update for what app caused it. It's probably an interaction with some other filesystem filter on my system, like Defender or Acronis True Image (which I am stuck using since every other disk imaging tool I've used is worse). Seeing this post on the front page has me wondering whether it's actually Backblaze's fault or it's Acronis, now... I've previously tracked down random system freezes caused by some part of the NVIDIA driver interacting with one of my monitors, where the first unlucky process on my system to call certain graphics APIs after a boot or wake-from-sleep would cause the video driver to hold a lock and enumerate display modes for 10+ seconds. The end result was a "frozen" PC still responding to input, just unable to send new pixels to any of its displays. The fun part of that one was that profiling would blame these freezes on whatever user mode process was unlucky enough to make that graphics API call - Steam's browser overlay, Visual Studio's WPF rendering, the list goes on. The troubleshooting process for this one was expensive because I got to the point of replacing components before I figured it out. I'm curious whether people who daily drive mac or linux encounter these sorts of system configuration gremlins. My experience using linux on servers and VMs has had some situations like this but I don't know whether the everyday experience just running Linux or OS X on bare metal is actually perfect at this point. |
|
Friend of mine dailies Arch. He described a few days ago a situation where he stopped being able to take screenshots from one day to the other, eventually finding out the root cause thanks to this fix: https://github.com/flameshot-org/flameshot/pull/4127
Whenever Linux package management and shared dependencies are mentioned, people always seem to be quick to mention how it's good for security that you can upgrade dependencies without the consent and knowledge of the developer of each software you're using. To me, issues like this come to mind instead. Or how I heard multiple times acquainted developers complain that packagers modified their software downstream and broke it in some ways, only for users to come complain to them instead of to the distribution.
There's a recent(?) trend of circumventing distro repos and static linking things though, and I work with Go software pretty often, which I believe static links by default: they're a joy to deploy and use. Just nice, single, self-contained binaries. But it's really not the "one true Linux way" from what I can tell, so I'd imagine it's pretty against the grain, which should tell you a lot about the situation overall. I know I'm not itching to switch, and these are only a sliver of my gripes too.