I am so incredibly tired of typing a command in Windows and getting yelled at because I forgot I was not in a bash shell. I saw the Microso...
I am so incredibly tired of typing a command in Windows and getting yelled at because I forgot I was not in a bash shell.
I saw the Microsoft Build 2026 announcements yesterday. Most of it was the usual corporate AI noise, but buried in the dev blog was something that actually matters. They are shipping Linux Coreutils natively in Windows.
Fixing the Terminal and Setup Drama
I do not know who finally lost the internal political battle at Microsoft over this, but thank you. I do not want to boot up a full WSL instance just because I need to grep a massive log file. I do not want to install outside ports. I just want the basic tools that literally every other operating system uses to just be there when I open a terminal. And now they are. They finally admitted the Unix way of doing things won.
Then there is the laptop setup problem.
Every time my company hands me a new machine, I lose an entire Tuesday. Digging through path variables, installing node, remembering where Windows hides the checkbox to show file extensions. Microsoft is finally fixing it with these Developer Configurations using WinGet. You make one config file. You run one command. It goes and fetches your editor, your frameworks, sets up your Git credentials, and flips all the stupid hidden OS settings automatically. It is insane that we had to wait until 2026 for a native version of what Mac guys have been doing for a decade, but I will take it.
The AI Hardware Push and Why I Am Skipping It
The rest of the event was just Microsoft trying to sell us AI hardware.
They spent a ton of time on "Microsoft Execution Containers" or MXC. The pitch is that since people are building these autonomous AI agents, you need a way to stop them from accidentally formatting your hard drive when they get confused. So MXC is basically a playpen. You lock the bot in a container where it can only see one folder.
Which is fine, I guess. If you are actually building rogue AI bots on your local machine, cool. But the overhead for this virtualization is going to be brutal. They demoed it on this massive new Surface RTX Spark Dev Box. Nobody's IT department is approving the budget for a petaflop machine just so a local bot can write boring code.
They also showed off an "Intelligent Terminal" that constantly watches your command line. If a script fails, it reads your error and pops open a side panel with the fix.
I am never turning that on.
I work with production databases. I am not having a background process reading my shell output. I do not care if Microsoft swears the telemetry stays local. It is a massive security liability and it is creepy. If my build breaks, I will figure it out myself.
So yeah, the Coreutils and WinGet updates are huge. The AI stuff can stay off my machine.
