Yes, both the Ally and the Go are sold in Australia. However it's also quite easy to order a "grey import" Steam Deck from Amazon, which is what I did. I'm guessing the sheer number of Steam Decks that have been sold into Australia that way are factoring into Valve's decision, because anecdotally among my peers the Steam Decks owned outnumber the Allys 4:1. Pretty impressive for a device not officially sold here.

I agree but I do have a little issue with the "wasting resources" part, that's a very anthropocentric view to take. There's an entire ecosystem of organisms that would love to use those resources, and in many cases leaving the carcass behind is better for that system than taking it away and depleting it of that biomass. There's obviously a lot of "ifs" involved but I wouldn't generalise by saying that because a human didn't get to eat it the resource was "wasted".

It's unfortunate that our ancestors have left us with this kind of ecological trolley problem, where in order to keep the system balanced and prevent collapse we're obligated to go out and kill a lot of creatures, but such is the world we've inherited.

Yeah there's not nearly enough damage to the back of the car for it to have hit so hard as to launch it into the air. Plus you can see yellow paint on the ground where the bollard was clearly laid over. OP is right.

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.

This isn't the first time such a vulnerability has been found, have you forgotten spectre/meltdown? Though this is arguably not nearly as impactful as those because it requires physical access to the machine.

Your fervour in trying to paint this as an equivalent problem to Intel's 13th and 14th gen defects, and implication that everyone else are being fanboys, is just telling on yourself mate. Normal people don't go to bat like that for massive corpos, only Kool aid drinkers.

It's how I've always interpreted it. The oft-cited saying is "you can't outrun a bad diet"

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.

Unfortunately this is a separate issue. The main problem that is blowing up now is that the CPUs are rapidly degrading to the point of failure even with completely standard settings and normal usage. And ironically, boosting the voltage to solve the issue you're talking about might then accelerate the degradation issue, because the leading theory seems to be that the high voltage that i9s use is frying the ringbus.

All around just a terrible situation for Intel and their customers

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

The thing he replied to is a modified copypasta, it was made as a joke