this post was submitted on 16 Apr 2024
807 points (89.1% liked)
linuxmemes
21190 readers
880 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
On my end, like --
I have about as many tech issues with Windows as with Linux -- It comes with me enjoying tinkering as a hobby I think?
BUT, and this is important, when shit breaks on Linux, there is always output on the terminal, or a log file, or something else you can check, and even when I don't know what to do about it, a simple copypaste of the error on internet search usually gets me some answers.
When shit breaks on Windows? HOLY FUCKING SHIT. It just sorta dies and leaves you in the dark with nothing to go on for troubleshooting. Windows wants to make computers into magic boxes that "just werk", but it never really gets there, and instead what you get is something that breaks just as often, but is a lot more opaque.
That BSOD with an emoticon lives rent-free in my head. Like who the fuck thought it was a good idea?
Also, even when you actually get an error message (which you probably had to dig through the awful mess that is the event viewer... Seriously, the only update they've made to it in the last twenty years was to split a bunch of things into a ton of individual logs that are more than painful to dig through), it's cryptic (if it tells you anything at all) and pasting it into search gives you nothing relevant, and quoting it gives you nothing at all (even the part that's obviously the generic part of the error), or if it does, it's a couple hits with people asking for help and either getting no replies, unhelpful replies that misunderstand the issue, or tells them they're asking in the wrong Microsoft support forum
Like... Come on, Microsoft. You clearly coded this error in the operating system. Put at least one page in documents online with at least something useful about it...
The few times I had to use the Windows Event Viewer I left having learned - Uh - Nothing except a newfound hatred for Microsoft. It's weird to navigate, and the logs are close to useless.
Application terminated due to internal error