this post was submitted on 06 Dec 2025
130 points (78.3% liked)
Technology
77795 readers
2255 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 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.