I’ve had two different arch based distros have issues when trying to update after long periods. I also had an Ubuntu server fail completely when doing a major version upgrade and had to restore it from backup. But then again I’ve also had no trouble updating an Ubuntu machine that was a couple years behind.

I’m on Fedora now for my desktop and it’s been great so far, but I also do updates at least weekly. My advice would be if you expect to go months between updates your best choice is probably Debian.

By hand you can feel that you’ve engaged the thread properly. If you just send it with a power tool then dealing with cross threaded fasteners is in your future.

Really not good enough from AMD. I wonder if Intel wasn’t a complete dumpster fire right now if they would still cut off the fix at Zen 3 (I doubt it). There’s really no reason not to issue a fix for these other than they don’t want to pay the engineers for the time to do it, and they think it won’t cost them any reputational damage.

I hate that every product and company sucks so hard these days.

Crowdstrike bypassed WHQL because the update was not to the driver, it was to a configuration file that then gets ingested by the driver. It’s deliberate so they can push out updates for developing threats without being slowed down by the WHQL process.

And that means when they decide to just send it on a Friday with a buggy config file, nobody is responsible but Crowdstrike.

Not quite true on the second part. It’s primarily Jatco CVTs that are reliability nightmares, and are what is used by Nissan. Subaru make their own CVTs which are widely regarded to be much more reliable.

Pretty much the entire poor reputation of CVTs derives from those shitty Jatcos but the tech itself wasn’t the problem, it was the execution.

Last I checked hexbear had something like 70% more total comments than lemmy.world despite only having a tiny fraction of the users. Sounds like bots to me