Microblog Memes

I think you're both right.

If you've always grown up Windows, then you generally know the steps to go through to try and fix it, which are oftentimes laborious and sifting through useless answers like sfc /scannow until you finally find some command you need to run like onedrive.exe /reset and about 12 other steps to get your OneDrive syncing (example problem).

Now you switch over to Linux as a fairly new user, oh my audio isn't coming from my speakers but is from the jack. Uhhhh, the Settings show it all there and working? Oh, here's a forum answer but it tells me to edit my pulseaudio.conf file? Where the hell is that? Oh, I found it but it's read only? Oh, I have to type sudo nano /etc/pulseaudio.conf into a terminal? Woah, what the fuck is this text editor?? I guess I use the arrow keys to move, but no mouse support? Alright I've edited it but what the heck Ctrl S isn't saving? Oh, the legend at the bottom says Ctrl O, and uhhhh, yeah overwrite? Now Ctrl X to exit, and uhhh, okay it's still not fixed but maybe a reboot fixes it. And if we fast forward 4 hours it turned out to be an audio driver.

You get my point. Linux is just different enough where if something breaks, and its something weirdly specific, its a lot of unknowns the user has to rapidly learn where they know these annoying troubleshooting things in Windows already. Linux does have really good forums and answers and documentation but its a learning curve regardless and that can be too much for a really casual user who doesn't have the time or will to follow through.