I can think of some niche cases where this might be useful(mostly HHD/SSD wear data; though bad actors have been able to tamper with those values without much difficulty); but overall this seems like throwing an awful lot of identifying data and a whole 'trust me bro' shadow subsystem at a problem that the data is unlikely to actually help all that much with.

This will be very good at fretting if the refurbisher swapped out RAM or mass storage; but it's not like onboard diagnostics are all that good at picking up the difference between a machine that has had a fairly hard life and now has somewhat dodgy ports and a bit of uncomfortable flex vs. one that sat on a dock most of its life and got unplugged only a handful of times; any any issue that the embedded diagnostics can pick up can also be picked up without any special recordkeeping by just running the diagnostics when you receive the device and verifying that it doesn't throw any errors out of the box.

If you've already got the trust me bro shadow subsystem I assume it's relatively cheap to propose having it keep more records; but I'm not really convinced of how much value is being added.

I don't know about you, but Intel SGX is deprecated/no longer exists. It only exists in Generation 8-12 CPUs, but Generation 11 and 12 CPUs received a microcode update that disabled it because of the problems it had.

And for anyone wondering, no, it was not AMD compatible. AMD has their own protection system based on ARM TrustZone technology. (And it has nothing to do with Intel ME or the AMD equivalent).

SGX was used by the UHD Blu-Ray folks, so it also means you cannot play discs on any PC now, making UHD Blu-Ray drives somewhat obsolete. (Now, you can RIP the discs just fine as they don't need anything special.).

The reason SGX was removed was due to a massive security flaw in it that let it leak out the secrets, and Intel deemed it unfixable and phased it out by deprecating it for Gen 11 and 12 before removing it.

Most businesses can't operate if the registers are down either, cashless or not.

Most inventory systems are computerized, and registers are linked with the inventory system so additional can be ordered. At the same time, the registers track the payment method so it can keep tabs on how much cash is in the register.

Thus, if the backend server goes down, the register goes down, and cash may not be accepted.

Now, a small business might be able to go back to pen and paper recording transactions, but that can be too hard - I've seen people break out the calculator just to calculate change, so basic math skills are lacking to the point I don't think many could work without a calculator.

The tax was probably going to be difficult to enforce. If Trump is going to take that as a win than it was a good sacrifice to make. Once he has his thing to brag about he will concede more.

That is probably the calculus behind it. You have to remember the G7 agreed to a minimum income tax which includes a DST, just Canada and France implemented it early.

This was a huge thorn in Biden's side, and Biden himself was trying to get it rescinded. No doubt in another timeline, Kamala Harris would be challenging it because it could potentially violate the USMCA/CUSMA agreement.

Trump wants "wins". So this counts - the Trump administration has said they are resuming trade talks. Plus, Trump needs a win soon - his "we have dozens of trade deals in July" is coming up. So far, all his trade deals have been nothing more than status quo or worse for the US, so now is the time to get Trump his "win" of screwing over the US.

Is there some problem particular to human DNA that they are looking to solve; or is this just an extension of the ongoing work on DNA synthesis(if you are OK with relatively short segments that has come down to being something you can just order, not nearly as exotic as it once was) but being hyped because there's some human cell genetic engineering at the end; rather than just meeting more aggressive targets for achievable lengths?

"Sane people use C for that" for embedded systems? That's a very "all i know I leaned from Slashdot" definition of embedded systems you must have

Dunno if you're a programmer or not, but if you're not extensively testing and verifying what you wrote before you put it in production, you're doing it wrong.

You have to verify and test *all* code. LLMs are great for producing a bunch of boiler plate code that would take a long time to write and is easily testable. The claim that LLMs are useless for programming flies in the face of everything happening in the ivoriest of towers of programming these days. Professionals in every major shop in the world use it now as appropriate. Sorry that makes you mad. I'm not young either. I've been producing C++ on embedded systems used by millions of people for 20+ years. Nobody doing serious programming takes the "LLMs are useless" opinion seriously anymore.

Ah yes, this moral panic is totally different than all the other times people have been whipped into a frenzy by an almost bon existent problem.

We have real problems to solve. I'll leave the fake ones to people like you.

You say 'involuntary psych hold'; I say 'MAU'!

So basically this is a new version of "Listening to Judas Priest will make you commit suicide", the Satanic Panic and all the other utterly moronic moral panics that make people afraid of unlikely things.

Oh good, another moral panic. If people aren't terrified every waking moment of their lives, someone hasn't done their job.

Having spent a whole hell of a lot of time lately on Gnome, configuring it and testing various configurations for rollout at the company I work for, all I can say is that it just works. There's a browser, and bizarrely, printers just work on Linux now in a way they just used to work on Windows, and it's now Windows, at least in an enterprise environment, where printing has become the technical equivalent of having your teeth filed down. Where work does need to be done is on accessibility, so we have one staff member who will stick with Windows 11 for now. Libreoffice's Calc is good enough for about 90% of the time, and Writer about 95%. We remain open to Windows machines for special use purposes, but most people after mucking around for a bit are able to navigate Gnome perfectly well, since once they're in the program they need to use, what's going on on the desktop is irrelevant.

On the enterprise back end, supporting global authentication has been around a long time, and if you only have admins who know how to navigate a GUI, then you have idiots. The *nix home folder is infinitely superior in every way to the hellscape that is roaming profiles, so already you're ahead of the game.

Enshittification, where even the most modest of talents is pushed aside by someone writing "Draw me a picture of a Florentine woman with a smirk" in ChatGPT.

It won't be long for lawyers to get in on the game - that because you were driving a vehicle with a tall hood, you knew it was going to cause more damage and thus you should pay more damages to the person you hit.

Get that going a few times and the insurance industry will adjust rates appropriately so people who drive big vehicles now have to pay for significantly more liability insurance because their vehicles are more likely to cause more damage to people.

Shouldn't take more than a few years for it to be sorted out - a few legal cases by ambulance chasers, and a few changes to insurance policies and now there's a market push for smaller vehicles again.

And most of the push to larger vehicles isn't CAFE or whatever. It's car companies - big vehicles are simply more profitable. They could sell you an econobox for $15,000, but they'd really rather you buy the F950 for $150,000 instead. That monster truck probably makes about 4 econoboxes worth of profit. I did NOT say make 4 times as much profit as the econobox. I said 4 econoboxes worth of profit. Probably 20 times the profit of the econobox.

TACO Tuesday is Canada Day this year, actually.