this post was submitted on 06 Dec 2025
110 points (77.0% liked)
Technology
77090 readers
2807 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Okay, wow. I've garnered plenty of downvotes on the Fediverse by not auto-hating many of Microsoft's new features and updates, I'm sure I've been labelled a "Microsoft shill" or somesuch in some folks' user notes. But this is just ridiculous.
The single most important rule Microsoft should have is "thou shalt not brick thy customers' computers with a routine update." Sure, it's not the most common set of triggering conditions in the world, but the problem is immediate and obvious upon booting up. How do they not have a test plan that would catch this?
Because the rigour and quality of work that is needed to do good software to get to market is insanely higher than the one required for keeping the money machine alive once you are a monopoly. So as you hire more and more to get your hands in as many pies as possible, have fewer and fewer experienced staff to train the new hires, and do questionable hires in leadership positions, the culture invariably shifts to doing less and less effort, or putting effort in the wrong place, and there you have it.
Now in Microsoft's case, the quality was never that high to begin with (but the scummy practices made up for that), and the pockets are deep aplenty, so I think we are in for quite the shitshow (it can, and it will, get even worse).
I'm convinced at this point they're letting the vibe coders write the OS updates. It's the only reasonable explanation for how they keep breaking core OS functionality that shouldn't even be getting updates.
I was going to try and defend them by saying that given the number of recent layoffs, and the push from the higher-ups, they're not necessarily vibe coders by choice.
But then I remembered, I don't give a shit about a company where devs think that rendering characters to a terminal emulator is a PhD-level problem, and that it's a good idea to use react native in your start menu, to only name two.
They are forcing AI on everyone in Microsoft.
There was an article about it, managers force to use AI to parse workers self reports produced by AI to make sure everyone and everything uses AI.
Because they fired the QA department years ago, in favour of non-rigorous testing by users crazy enough to run whatever Microsoft's version of a nightly build is. Because there's no testing plan, some sets of conditions never do get tested.
Holy shit I want to meet the kind of people who are willingly testing a nightly build of Windows. They sound fucking unhinged.
Looking at all the new features and how none of them have appealed to me with it being different attempts at forcing copilot I think the only happy Windows users are ltsc ones. Closest experience to a dumb OS that doesn't change and just installs and runs the programs you install and came with minimal bloatware compared to new regular Windows.