And the less you use Windows, the worse you get at using it. Luckily the bar for Windows competency is pretty low, just basic critical thinking skills and Google get you far.
Honestly, potentially the more you use Windows the worse you get at it. You come to accept the garbage, but the more you try to fix it the more it fights you and the less stable it becomes. A user who just doesn’t touch anything is probably better off.
Oh hell no. My basic critical thinking applied to googling has got me to a forum with the solution to wi-fi not working in the form of “meh, it happens. reser all network settings and reboot”. Which became my personal turning point of “fuck this shit, I’d rather have actually debuggable software”
/cooled down/
Well, your point read as “look at the problem, search for solutions and you probably will find them” stands, it is the low competency bar that triggered me: to even know where crash logs etc might be on Windows is far beyond even “power user” level
If you’re searching online for how to fix the problem… Couldn’t you also search online on how to find the crash logs? I fully get sometimes not having enough knowledge in a subject to even know where to begin searching, but “well, the first result wasn’t helpful, guess I’ll stop looking for an answer” and “it says to check XYZ, but I don’t know what that is. Too bad I don’t have a way to search for what things are” aren’t exactly difficult hurtles to overcome.
I only learned windows had system-level crash logs by reading someone’s post about many programs ignoring that and thus it being way less helpful than one might expect it to be, while on Linux it seems something that gets picked up quite early: the system can write “check logs using journalctl something-somethng”, vast number of posts asking to provide system logs with the commands to get them, various troubleshooting guides mentioning system logging.
Though in the end this difference can be traced to difference in philosophies: neither microsoft, nor most authors of online guides have a habbit of troubleshooting things this way
And the less you use Windows, the worse you get at using it. Luckily the bar for Windows competency is pretty low, just basic critical thinking skills and Google get you far.
You can make that point for any operating system, basic critical thinking could mean anything
You could but you’d be drawing a false equivalency.
I got an equivalency for ya
Pb(s)+2 HCl(aq)→PbCl2(s)+H2(g)
Honestly, potentially the more you use Windows the worse you get at it. You come to accept the garbage, but the more you try to fix it the more it fights you and the less stable it becomes. A user who just doesn’t touch anything is probably better off.
/triggered/
Oh hell no. My basic critical thinking applied to googling has got me to a forum with the solution to wi-fi not working in the form of “meh, it happens. reser all network settings and reboot”. Which became my personal turning point of “fuck this shit, I’d rather have actually debuggable software”
/cooled down/
Well, your point read as “look at the problem, search for solutions and you probably will find them” stands, it is the low competency bar that triggered me: to even know where crash logs etc might be on Windows is far beyond even “power user” level
If you’re searching online for how to fix the problem… Couldn’t you also search online on how to find the crash logs? I fully get sometimes not having enough knowledge in a subject to even know where to begin searching, but “well, the first result wasn’t helpful, guess I’ll stop looking for an answer” and “it says to check XYZ, but I don’t know what that is. Too bad I don’t have a way to search for what things are” aren’t exactly difficult hurtles to overcome.
I could, if only I knew they existed :)
I only learned windows had system-level crash logs by reading someone’s post about many programs ignoring that and thus it being way less helpful than one might expect it to be, while on Linux it seems something that gets picked up quite early: the system can write “check logs using journalctl something-somethng”, vast number of posts asking to provide system logs with the commands to get them, various troubleshooting guides mentioning system logging. Though in the end this difference can be traced to difference in philosophies: neither microsoft, nor most authors of online guides have a habbit of troubleshooting things this way
What? It’s easy to find a solution to WiFi problems, come on.
Usually, sure, but mine was just that. It helped, so kind of solution anyway
My great-aunt would like a word with you.