this post was submitted on 06 Jan 2024
253 points (93.5% liked)
Asklemmy
43962 readers
2086 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In my experience, if you have an issue on a Unix-like OS it’s almost always possible to diagnose and fix the problem. There is almost always a log file with extensive information. Unices are built from collections of simple tools so it’s often easy to find what exactly is going on and to isolate the problem for an easy fix.
Windows on the other hand is a black box. If something doesn’t work, you’re screwed. Error messages are often cryptic to the point of being little more than a 432 digit number. Most subsystems are monolithic monstrosities and isolating an issue is a PITA. Troubleshooting usually isn’t much more than randomly changing things and see what happens, or googling the error and hope someone else found a fix. Even if you manage to fix it, it’s often unclear what the actual issue was. It kind of reminds me of the magic/more magic switch.