whenever someone comes to me asking for help on windows, I first tell them straightway that windows is shit, and I know nothing about it. then I spend half an hour searching for answers to resolve the problem, only to curse it again and give up, before telling then again to use a better operating system(i.e., GNU/Linux).
Windows is a whole lot better documented than any Linux distro ever will be. Because of the fact it is the standard in the majority of businesses. So if you can’t find the solution, then that is on you.
yes, I don’t want to be get “skilled” in a proprietary disservice.
and no, distributions like Debian GNU/Linux, or arch has far better documentation. the quality of documentation also matters. they may not have 100 different “run sfc scannow” websites, but they will have almost any problem you can find on good forums.
To be fair, I’ve had some issues on Windows that have left microsoft support staff saying “yeah man Idk good luck hope you figure that out lol”. Meanwhile, on Arch, I’ve never had a problem that didn’t have a solution, or at least a clearly documented cause (which is almost always just as important as the solution) right there in plain text on the ArchWiki.
Plus, when a windows error happens, you usually just get a little message saying “It dun broke 🤷♂️”. Again, on linux, 9 times out of 10, I get a pretty detailed error message at least telling me what broke, and maybe even some hints as to why. I get that Windows has error logs, but I bever have to dig for that info on linux, it’s always presented to me because it’s important.
Does windows show logs? What documentation is going to help you when you don’t know the error. Most windows troubleshooting guides I’ve seen include 4-5 solutions and say try all of them maybe something will work if you are lucky. On linux you can find pretty much any bug on GitHub or an online forum.
Edit: ignore this guy lol. Just seen him in other comments in this thread. Dude is saying skill issue when he’s literally scared of a terminal.
I work in a Windows environnent but often use Linux at home. I find that the level of difficulty is equivalent once you’re familiar with either OS, their general design, and how their management tools are meant to work. It’s mostly a familiarity problem. You don’t use Windows regularly so you have no idea where to even start troubleshooting, or how to tell at a glance if the instructions you’ve found pass the sniff test.
Plus, it’s always considerably easier to troubleshoot your own shit than to troubleshoot some random person’s jacked up configuration where you don’t know how they use their machine or how they managed to fuck it up.
The biggest difference I find is that Windows has such a massive user base that any “user based” help (like the microsoft support forums, yuck) is far more likely to be written by some shmuck that doesn’t know what they’re talking about than you see with Linux. Alternatively, it’s just content farm site after content farm site regurgitating shit advice stolen from the users who don’t really know what they’re talking about. Finding useful information and guides can be more difficult.
yeah, my machines have been windows-free for almost a decade, and in the development field, I rarely see it. So, it’s alien and disorienting to me.
but even then my experience with windows has been less than optimal. I had to install many good services like henrypp’s simplewall just to stop windows from phoning home. not to mention removing other bloat.
with GNU/Linux, I know my machine will do nothing like that without my explicit permission.
whenever someone comes to me asking for help on windows, I first tell them straightway that windows is shit, and I know nothing about it. then I spend half an hour searching for answers to resolve the problem, only to curse it again and give up, before telling then again to use a better operating system(i.e., GNU/Linux).
Ah, so it is a skill issue for you?
Windows is a whole lot better documented than any Linux distro ever will be. Because of the fact it is the standard in the majority of businesses. So if you can’t find the solution, then that is on you.
yes, I don’t want to be get “skilled” in a proprietary disservice.
and no, distributions like Debian GNU/Linux, or arch has far better documentation. the quality of documentation also matters. they may not have 100 different “run sfc scannow” websites, but they will have almost any problem you can find on good forums.
To be fair, I’ve had some issues on Windows that have left microsoft support staff saying “yeah man Idk good luck hope you figure that out lol”. Meanwhile, on Arch, I’ve never had a problem that didn’t have a solution, or at least a clearly documented cause (which is almost always just as important as the solution) right there in plain text on the ArchWiki.
Plus, when a windows error happens, you usually just get a little message saying “It dun broke 🤷♂️”. Again, on linux, 9 times out of 10, I get a pretty detailed error message at least telling me what broke, and maybe even some hints as to why. I get that Windows has error logs, but I bever have to dig for that info on linux, it’s always presented to me because it’s important.
Windows documentation be like:
Does windows show logs? What documentation is going to help you when you don’t know the error. Most windows troubleshooting guides I’ve seen include 4-5 solutions and say try all of them maybe something will work if you are lucky. On linux you can find pretty much any bug on GitHub or an online forum.
Edit: ignore this guy lol. Just seen him in other comments in this thread. Dude is saying skill issue when he’s literally scared of a terminal.
I work in a Windows environnent but often use Linux at home. I find that the level of difficulty is equivalent once you’re familiar with either OS, their general design, and how their management tools are meant to work. It’s mostly a familiarity problem. You don’t use Windows regularly so you have no idea where to even start troubleshooting, or how to tell at a glance if the instructions you’ve found pass the sniff test.
Plus, it’s always considerably easier to troubleshoot your own shit than to troubleshoot some random person’s jacked up configuration where you don’t know how they use their machine or how they managed to fuck it up.
The biggest difference I find is that Windows has such a massive user base that any “user based” help (like the microsoft support forums, yuck) is far more likely to be written by some shmuck that doesn’t know what they’re talking about than you see with Linux. Alternatively, it’s just content farm site after content farm site regurgitating shit advice stolen from the users who don’t really know what they’re talking about. Finding useful information and guides can be more difficult.
yeah, my machines have been windows-free for almost a decade, and in the development field, I rarely see it. So, it’s alien and disorienting to me.
but even then my experience with windows has been less than optimal. I had to install many good services like henrypp’s simplewall just to stop windows from phoning home. not to mention removing other bloat.
with GNU/Linux, I know my machine will do nothing like that without my explicit permission.