Same with me. I didn't feel the need to choose or confirm something every boot on day to day use. If I need to boot somewhere else, then I could always go to the BIOS/UEFI

Because it adds something that is not essential, so it is not "simple". If package A depends on package B with an incompatible license then it needs to provide a means to specify alternate packages. Arch follows upstream with best effort possible, so changing dependency could be seen as breaking that. However, pacman already supports choosing alternate packages during installation so technically they could add it, but how many percentage of users are needing that convenience? Not to mention the arch team will need to maintain said list of alternatives for every dependencies. If you want, you can add it yourself via pacman hook to prevent you from accidentally installing non free software, or write a wrapper for pacman, or use other distro like Parabola.

Well, because Arch tries to be simple and pragmatic. The way the official repo is organized speaks volumes about its philosophy. ~~Just read their FAQs~~

My bad, not FAQs, but their explanation page

Depends on the application. When the user is able to set the schema via database, then you cannot assume the shape of the data.

Well, "just works" depends on how you define it too. But yeah, most of the "basic" stuff just works. But I will not rule out the possibility of unsupported HW just because I have my fair share of it too. For example, I'd say a keyboard is working if they are able to be used as an input device. Even without the customization or sleep, or wake from sleep. Granted, the issue being unrecognized or not working at all is very much borked tho. Hence why I request the details of the mouse itself.

Now you mention degraded performance and glitches. Yes, I do know that. But as I said, my statement regarding the wrong driver usually entails a lot more dramatic bug than a stutter on only known 2 games. Further investigations are needed to correctly decide if it is the driver or not since we know that a compatibility layer is also playing a part here. It is also why I suggest searching the protondb to check the current support for the game. Linux gaming, as good as it is now, is not perfect yet.

Wait, Fedora is bleeding edge too? I don't know that

But the recommendation can make better inference if they have more data wouldn't they? What should have happened is opt-in for a better recommendation.

As someone who recommends Arch to new users that have some familiarity with CLI AND also likes to tinker, I will always advise to check their wiki and forum. Check for the very specific problem you're having. Even the model sometimes helps. From other comments, I see you're mentioning logitech, maybe this wiki entry will help, but maybe it won't. In which case, search for more information. Check their wiki entry for other logitech mice, for wireless mice, for general mice.

Now, onto the next issue, what do you mean by not launch right? From there, maybe I can help with the issue.

This is also why I recommend this to someone that would like to tinker with their system. Arch requires a lot of reading. But once you understand it, it becomes "yours" and you obtain a lot of knowledge about the system that you're using.

Now, for everyone who doesn't like to tinker, use bazzite. I heard that it just works™.

I mean, if I understand it correctly, audio signals are additive so you don't need to do fancy instrument changing. Simply add the sample of different instruments to the audio buffer and those can be played. If someone knows better about acoustic theory then please correct me.

TIL about bus factor

i

Technically they could by manually verifying the cert from somewhere offline.