I feel your frustration and honestly with 25 years of desktop Linux experience I've come to the conclusion problems with software are most common in the deb packages. For better or worse Debian maintainers patch and hack apart software to work 'the Debian way' and that almost always introduces quirks and issues for end users that are never documented well.

Like for example I've been playing with Kodi and as a deb package you can't install some (but not all) add-ons through the built in UI, you have to go find special apt packages for them and install those outside the Kodi UI. Nowhere is this documented or visible to users--Kodi's webpage doesn't concern itself with how Debian packages it so no mention there, and Debian itself is a black hole of information for end users. The exact same issue is present with RetroArch and its Debian packages version. My bottom line is I always pick a deb package as the very last option and expect pain or confusion when doing so.

If it did matter there would be detail as to why. It doesn't. One of them was buggy, but again does not matter which one.

> or should I just "git gud"

The opposite. Just blindly click on one. If it works you are done, if not click on a different one.

You are really, really overcomplicating this for no reason.

Nope, this is a very good point. Because for example you can't use Python/Selenium with a Flatpak version of Chromium, while you can with .deb version on Pop_OS. If you have no clue what the difference is between both of them, you would have no idea why it's not working in one case and not in the other.

Disagree. That is a bug that should be fixed, not ignored.

Same with selinux: Lots of "advice" was just to turn it off completely.

> You would have no idea why

Yes, file a bug to get it fixed instead of leaving other users standing in the rain.