Why he should *he* leave? You're the one who sucks

Even a stopped clock is right twice a day.

This sounds like it was written by someone who actually knows what they are doing, so I assume that they know better than I; but I am surprised to hear that it is impersonating a system dll; since (in all comparatively recent windows versions) system components are signed. Absolutely tons of fuckery you can do to them and around them; but if dpapi.dll doesn't have a signature that checks out the mechanisms that try to keep OSes up and running on marginal hardware subject to random power loss will likely eventually object and attempt a repair, even if there isn't any more paranoid EDR tooling in place.

Is the on-disk copy of dpapi.dll untouched and only the in-memory instance tampered with?

I just can't believe that It was the guys with their finger on GPU allocations, not just the expendable PC OEM they were trying to throw under the bus, the whole time. Whoever could have guessed?

The descendants of Ogg have renewed the ongoing lawsuit against the descendants of Zogg alleging that Ogg dropped a rock on Zoggs foot in a cave one fine day and it was really ouchie! Anthropologists are working around the clock trying to restore the cave paintings documenting the original complaint made to the tribal chief in 30,001 BCE.

That's because of all of the inbreeding. A is the CEO at one place where B sits on the board. Next door, B is the CEO and A sits on the board...

Exactly that. Many seem to have forgotten that hospitals were absolutely slammed early in the pandemic and that medical care in general suffered.

Not to mention an increase in damaging severe weather.

Even people who like it warmer probably don't like having their house blown away to Oz.

Unfortunately, it has a way of becoming your problem as they strain medical resources, continue to drive global warming and run around spreading their infectious diseases.

The key is to use the AI more sensibly. Let it find things in code. Even let it look at possible bugs in the form of where does it "describe bug". Even let it propose changes. DO NOT let it make the changes, just show them. Do not just take it's word for it, take the shown code as a starting point but re-do it for maintainability after sanity checking it.

THEN it can be a useful tool.

I love that you didn't explain what the effect of this will be on the "not smart kids." Do you think they're going to hit the books and do a bunch of non-optional homework to learn the material? Have you met a single child?

You make a good point about how things are different "now" vs years ago -- the recent invention of ...homework.

Maybe you should consider thinking about thinks for more than 5 seconds before sharing your dumbfuck thoughts with the world

The available information isn't terribly specific; but on the surface it doesn't sound any deeper into application internals than it already does.

You can certainly go deeper into etw trace hell; but Task Manager knows how much CPU time you are eating, your memory consumption metrics, your network traffic, and has a (currently less granular) look at your consumption of GPU time. It also having a view of consumed NPU time seems totally analogous for a new flavor of coprocessor. Only one that might involve gory poking at the application(though I'd assume would be more logically pulled from the GPU driver) would be distinguishing "GPU Neural Engine" from GPU utilization generally.

It's not the SCREEN that does the damage, it's the brain rot the screen is used to access. Also the amount of time speant with the screen. Moderation is good. This shouldn't surprise people, but since it is a nuanced understanding and not just screen bad!, it will.

BOTH screwed up. The system shouldn't have made the match and the human should have done a better job seeing that the match was wrong. I'll go one larger and say the people who created the procedures screwed up because they didn't make allowances for the possibility of the first two screw-ups.