You're viewing a single thread.
I think both Windows and Linux are scary when you want to exactly fits you need.
In using linux I started to know what is a DE, kernel, kernel argument, GRUB, systemd, selinux, etc. and I am the person that want to learn NOTHING about my OS, they just unfortunately pops up during troubleshooting.
So is Windows, device manager, ipconfig, registry table, chocolatey, cmd vs powershell, WSL, and many more. But I would say, if you don't care about bloat and ads, and are willing to make stupid compromises, like copy a email to a notepad, so you can see it while drafting a new email. Windows might breaks slightly less often than linux depending on your hardware. But that doesn't mean Windows don't break, in fact Windows broke just in the first linux challenge video.
For Linus's experiment, I don't really think it is a fair comparison between Linux and Windows. No one is going to learn a OS in a month, and expect to have the ability to not harm themselves, not on Windows not on Linux not on macOS.
But it does serve as a good simulation of a busy Windows enthusiast moving to linux. Personally, I don't think this should be the only criteria to judge the linux eco system, but it is a important criteria, and linux has many things they can improve in this regard (and they are indeed improving).
However, popOS installer for steam breaking DE is a legitimately rare event, and it happens to the most popular tech youtuber is even more rare...
Shit happens 🤷. It happens to milti-billion dollar companies as well, like MS. In fact, it happens a lot more frequently (and it's more destructive) than it does with Linux or any other POSIX based OS. I have yet to see an update deleting all my personal files in
/home.Troubleshooting problems is about the same IMO, if you're familiar with the OS and how things work (in general). You just use the terminal more in Linux, since you'd have to open the file manager as root in order to troubleshoot, and that brings a whole other set of issues, like file permissions if you happen to copy a file to, let's say
/home/<username>/Desktoptemporarily, for troubleshooting. Ah, but now the file has root permissions, not the permissions your user has, and root is the owner of the file, so basically, your user only has read permissions, that's it. You can't move or delete the file. In order to move it or delete it, with a GUI, you'd have to open up the file manager as root again and do it from there. And that is why using the terminal to accomplish these things is so much simpler. You just addsudoin front and that's it, the command will do whatever root could do. And then you realize that just copying and renaming the file tofilename.bakin the same location where the file originally resides is so much quicker and better. You can delete or move the file just by addingsudoin front of the command, no file manager needed.So yeah, troubleshooting is more or less the same IMO.