Comment on Windows Is Adding AI Agents That Can Change Your Settings
lmmarsano@lemmynsfw.com 2 days agoWhat if we had all these configuration knobs & switches controlled by a configuration file, and to replicate the configuration, we could just share the file? Maybe we could call it declarative configuration management?
That already exists (partially) & could be developed further?
yggstyle@lemmy.world 2 days ago
Shit you know … I feel like Microsoft has done that with the registry and gpedit… a real shame they seem to disregard those controls when it suits their new advertising model… erm… bing engagement system.
We’ve had config files and scripts for ages. Most of us are pissed that all of those methods half work or are depreciating away for no reason other than some UIx twat couldn’t be bothered to hook something properly so they just reskin an element and misplaced half the functions. Bonus points if they did so while wasting more system resources, breaking their own search pointers, and infuriating sysadmins and users alike.
Now I’ll give you that new methods can absolutely be implemented and replace (effectively even) old, longstanding methods… but Microsoft has utterly missed the boat on this. Repeatedly.
To your ai statement: Look I won’t comment on where AI may or may not end up in 5 years but I know that getting a black box to hallucinate 40% less has got to be infinitely harder than indexing a filesystem, a series of .lnk files, and maybe… maybe some control names. Considering they had most of that working (even if you had the index disabled!) in windows 2000 / 9x / XP it blows my mind why this has not been resolved when it’s basically a meme at this point.
No other OS has this basic problem. Why are we building onto something when the foundation is shit? I’m certain there’s developers at Microsoft that have skills - but I’ll be damned if I see any of them taking a step forward without two back.
Block kernel level driver access to shit. Maybe improve resource usage on existing processes. Fix the goddamn search. Don’t bury a setting behind ANOTHER useless dialog. Fix something - don’t jam more useless shit down our throats. We don’t need new: we need working.
At the rate we’re going the next windows version (maybe even 11) will intersect with Linux (pick a flavor) in terms of compatibility, usability, and stability with Linux doing literally nothing but existing. To be fair every other version is hot garbage. I’m sure we can ride out 11 on 10 … right?
lmmarsano@lemmynsfw.com 1 day ago
They’re still around and the various configuration technologies tap into them.
Pretty much the case here, too. It mostly works, and the parts that don’t are super annoying & require ad hoc script-fu.
Yep, configuring Microsoft has sucked incredibly hard compared to free OSs. Managing plain text configuration files in
/etc&~/.configis refreshingly nice compared to the bolt-on weirdness hidden behind various interfaces in Windows. It’s cute getting an error to contact your administrator when you’re the administrator.Attention in that area is extremely late & overdue, so I was happy to see something like
configuration.dsc.yaml.I see AI mostly as an assistant whose work I review. I might give it a fully written text, tell it to clean up my clunky language, then review it. Or I might ask it to provide some answers with references & review those references.
AI won’t fix broken foundations.
I try to avoid Windows altogether if I can & confine it to less serious work.
yggstyle@lemmy.world 1 day ago
I noted this in a dismissive way… Yes they exist; but as mentioned - depreciation and outright ignoring settings has become a thing Microsoft has willingly done if they feel “they know better.” (Reboots and update times are an excellent example of this.)
Locking some things out makes sense. This exists in all OSs… what is maddening is Microsoft almost aggressively working against admins. Want local accounts? No sir. Not allowed. Not unless you remove the network card, face the PC east at precisely 2:30 am, and type a 40 character rolling code into the terminal that appears… twice.
While I agree - the point I was stressing was that many admins had perfectly workable scripts and methods that used the existing tooling as it was intended… and it’s mostly been fine. With their recent push into spyware inside ™ … ahem engagement … they seem to be actively punching holes in this to force management to their cloud resources which surely will not ever have problems …
Agreed. It does have the means to save some time - but it’s just not “cooked enough” for me to use it on any meaningful level. Personally speaking.
Sadly some things I work with just don’t play with wine just yet otherwise I’d abandon it entirely. I’d personally love to, though.
What really bothers me is late in the patching cycle windows 2000 was borderline amazing and could be tuned to an absolutely minute footprint. If it was fully updated for x64 it would have been just about perfect. Nothing got in your way: very minimal UI with “just enough” modern features. Getting to almost any administrative interface was at its lowest “clicks to access” of any (subsequent) windows version. NT dna.
I may just have rose tinted glasses but from basically that point on it was all just bolted on UI garbage that got between you, your resources, and most importantly what you wanted to be doing. And when it comes down to it - regardless of what os were talking about - something has gone horribly wrong if that is the reality.