Windows has never felt more archaic than now. I can't imagine trying to do work on a Windows machine in the age of LLMs.
If there is anything that LLMs are rock solid at these days, it's unix terminal usage.
If there is anything that LLMs are rock solid at these days, it's unix terminal usage.
Try starting from a blank slate Windows machine and making a commitment to only changing settings via PowerShell, and ideally only declaring them using DSC. You'll soon discover settings where the best you can do is snapshot the registry, change a setting in the GUI, snapshot the registry again, then take a diff so you can write the registry change into your PowerShell automation. If you're on a corporate machine, you'll also likely find many corners of PowerShell that you need closed off to you, anyway.
At the end of the day, Windows is not friendly to automation because it's not CLI-first (not culturally and not technically).
I realize text files can be processed by utilities for working with text files. And text files can be read by humans without any tools, and in that sense are rather universal.
I wonder what I'm missing.
I'd go so far as to think an OS that had a database at its core, or perhaps a persistent lisp would be even more programmable and legible.
Maybe better tools for dealing with structured data would help this?
If you don't like the Windows style of configuration, run powershell on linux - it's awesome there too!
That’s easy: you activate WSL and then ask the LLM how to get networking and stuff working since they changed it with WSL2. You need a config file flag to setup network mirroring now.
I used to hate working in Windows, but now it feels roughly comparable to Mac (though at the risk of inciting an OS war, I do feel like Linux still beats both out...)