Linux

I don't know how Manjaro plans to do it, but Universal Blue distros have access to the entire set of dnf repositories, including non-free packages. You run rpm-ostree install, and it layers the package you want. Each system update re-layers the custom package layer after upgrading the system layer.

But since this is pre-alphaware, it's kind of early to be passing judgement on how/if they'll have access to the AUR and whether you could layer packages. Seems like the "safety" aspect is served through having an immutable system, which ensures end users have the same base as everyone else.

And it's fine if that's not your cup of tea. Sounds like it's not. Arch, openSUSE, Debian, and their mutable descendants aren't going anywhere.

I don't know for the AUR, but the regular repos seem to be already accessible. You can try them with pacman, but the installed packages will be deleted at the moment of the update, or you can create a custom image and add the wanted packages which will be reinstalled at every update.

I haven't had any problems with Bazzite, either, save for figuring out how to install Private Internet Access's client, but that's not immutable distros' fault. The fault lies with PIA for not packaging their client in a sane way.

I couldn't find jack shit, other than posts where people were saying that it sits within the immutable part of the distro and the profile manager just opened some temporary profile folder, with the permanent path being invalid / nonexistent. If that information is wrong then they should work at least on their documentation, which I checked for FF profiles and could find 0 entries.

I could probably summarize your experience as "skill issue".

Blaming users for a lack of proper UX is always the best excuse.

This is simply false as pointed out by others already.

Yet the only information I could find by other users of the distro. I even checked the official documentation, which contained 0 information on Firefox profiles. The FF profile manager only led to temporary folders and the absolute path led to an inexistent / invalid one (the one you'd expect them to go normally). So yes, I guess my skills are low, but so is the possibility for me to even learn anything when the only barely scrapped info I could find is wrong.

I wouldn't be surprised if you just searched this through your favorite search engine and settled with whatever random solution you came across instead of relying upon RPM Fusion's documentation on the matter.

No, that and the rpm fusion install page is quite literally exactly what I used. Then no applications would launch, no UI functions would work and after I hard reset the PC it wouldn't show me anything but a broken welcome page, which, when closed, left me with a blank black screen and my mouse cursor. I'm not sure what else you would expect me to do when following seemingly official command guidelines. But I guess it's still my fault after all.

While this could be true, I wonder what prevented you from sticking with any one of them.

Let's see...

• Manjaro: Lots of criticism from others, ironically ran 2 years without major issues. But I wanted to switch to btrfs and EOS was hyped up to be a better version of a simple Arch installation.
• EndeavourOS: An update nuked the bootloader after a few months. Could not figure out how to fix it since "guides" were using non encrypted devices as an example and were expecting user knowledge already. Tried asking for help in the official forums and got gaslit and insulted by users instead to the point where the mods had to close and hide the thread, suggesting I make a new one if I still need help. I decided it was better to leave that toxic cesspool & distro.
• OpenSUSE: Installation failed to create partitions. When I eventually got past the issue and got it installed I could not switch resolution down to 1080p because it would just turn my screen into a stretched pancake mode. Could neither find a solution or any information as to why it cannot do something as basic as this, so moved on.
• Nobara: Nuked its Plasma setup, leaving you with a blank screen and the broken crash reporter. Could not find any information anywhere on it so I tried using Timeshift via rescue terminal and it would just error out because it failed to mount boot partitions or whatever. Used a live usb environment and ran GUI Timeshift, mounted the snapshot partition and restored the last snapshot that way, seemingly without an error. But on a reboot it then became unbootable with even more errors about the partitions. Again, no matching threads I could find that would be able to help me.
• Bazzite we already covered came after.
• Fedora: Since many people said most of my issues come from using a fork of a private guy I was expecting major polish. But as already covered they don't have an easy way to enable the most basic multimedia playback and their official how-to broke the system.

It's definitely a lot harder if you've got major skill issues.

Especially since absolutely no one is willing to help and rather throws insults and personal attacks around when facing people who struggle with all the major bugs.