this post was submitted on 15 Jan 2026
753 points (97.2% liked)
Technology
78748 readers
3553 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
The only problem I've had so far on Linux was due to my RAM breaking. Same shit could've happened on Windows. As much as everyone talks about needing "manual intervention" in Arch, I had to do the same shit on Windows after a bad update pushed unsigned USB drivers (which I was unaware of, I only saw the blue screen) then once I did a system restore it just failed after wiping my hard drive despite only using tools from Windows itself. I ended up having to get a third party tool to fix it all, because the vhdx files Windows made assumed my computer was UEFI despite only supporting BIOS. It was a mess.
The moral of the story is: Windows still has these problems, people are just more used to solving them so it doesn't feel like they're solving a problem.