“Did I give you permission to delete my D:\ drive?”

Hmm… the answer here is probably YES. I doubt whatever agent he used defaulted to the ability to run all commands unsupervised.

He either approved a command that looked harmless but nuked D:\ OR he whitelisted the agent to run rmdir one day, and that whitelist remained until now.

There’s a good reason why people that choose to run agents with the ability to run commands at least try to sandbox it to limit the blast radius.

This guy let an LLM raw dog his CMD.EXE and now he’s sad that it made a mistake (as LLMs will do).

Next time, don’t point the gun at your foot and complain when it gets blown off.

As your everyday, typical guy, I want nothing more than agentic synergy in my converged Windows Experience. I’m glad Microsoft is finally listening to what regular people want!

I think it’s pretty clear the “Rust experiment” has failed. You don’t need to be the Amazing Kreskin to know how this plays out. The writing is on the wall: Rust faces a bleak future.

It’s time developers got serious and rewrote sudo-rs in a serious, tried-and-true systems language, potentially C or C++. Only then can system administrators sleep soundly at night, feeling safe from the type of bugs introducing Rust to a mature ecosystem can cause.

Why main? m is much clearer

I don’t care which one you use, just don’t change it once it’s established. So many legacy Yocto projects got broken cause open source libraries changed their branch names.

This was one of the arguments when the renaming was first proposed. “Just rename it, it won’t break anything! It’s only racists that want to keep the name!”

Sure, except for all the CI/CD scripts, release scripts, etc that all have “master” there and are now broken.

I know of a company that their entire CI pipeline was broken overnight because some “helpful” person renamed the branch to master but didn’t bother checking out their pipelines…

It’s a scary amount of projects these days managed by a bunch of ZIP files:

• Program-2.4.zip
• Program-2.4-FIXED.zip
• Program-2.4-FIXED2.zip
• Program-2.4-FIXED-final.zip
• Program-2.4-FIXED-final-REAL.zip
• Program-2.4-FIXED-FINAL-no-seriously.zip
• Program-2.4-FINAL-use-this.zip
• Program-2.4-FINAL-use-this-2.zip
• Program-2.4-working-maybe.zip
• Program-2.4-FINAL-BUGFIX-LAST-ONE.zip
• Program-2.4-FINAL-BUGFIX-LAST-ONE-v2.zip