With Windows, even if I don't know the exact steps to do something, I can figure it out because some smart people have done a lot of UI design work to make that

With Windows, even if I don't know the exact steps to do something, I can figure it out because some smart people have done a lot of UI design work to make that so. Off the top of my head, I can't tell you the exact steps on how to change the mouse speed on either Linux or Windows - I don't do that often enough to memorize the process. But I know in Windows, it will involve navigating to the Settings app, so I go there. The mouse is a device, so I click on "Bluetooth and Devices" in the left taskbar. I then click on "Mouse, which takes me to the mouse speed. The process in Linux depends on your DE. If you use something like KDE, the process is similar to Windows; but if I'm using i3, I'll probably need to go into the x11 settings. But I can't google "how to change mouse speed in Linux", because again, Linux isn't an OS even though it gets treated as one. So the end result is the same, I can change the mouse speed in both OSes. But Windows definitely required no prior research, whereas Linux may or may not have required research depending on how the user set up their machine. And if I was new to Windows, I could google "how to change mouse speed on Windows" and get a straightforward answer. You could argue that on linux, I should have googled "how to change mouse speed in Ubuntu/Pop OS/KDE Neon/etc". The problem with that is that sometimes I can use generic Linux instructions, and sometimes I use distro-specific instructions. People actually point non-Arch users to the ArchLinux wiki! Incidentally, I looked at the general recommendations page on the ArchLinux wiki [1], and found it seems to recommend alsa as a default and pulseaudio if you want some more complex features. Maybe this is wrong, maybe there are differing opinions in the community. Again, there's no way in Windows that you would run into two competing ways for sound to be sent from programs to your headphones/speakers because of the unifying force of the company. (Personally, I've always wondered why audio isn't just part of X11 or Wayland, since X11 and Wayland seem to control everything else the user interacts with.) I also know from personal experience that Vim vs NeoVim is a complicated discussion and full of a lot of drama over the maintainers of Vim being hard to work with - yet another problem that wouldn't happen at Microsoft because you have a management structure that can deal with these sorts of problems without defaulting to the lazy open-source solution of "just give the customer more options." 1: https://wiki.archlinux.org/title/General_recommendations#Sound_system https://wiki.archlinux.org/title/General_recommendations#Sou...