@opal
- fedora: more or less nice, just werks, but i have to use flatpaks eventually, and flatpaks fucking suck sooner or later in different ways.

-opensusan: dealing with vendor changes and wondering if what i did is fine/supposed to be done, little documentation/stuff online.

-debian unstable: would work, but many packages are still old as shit. firmware? from fucking aug of 2021. need it up to date for i915.enable_guc (this thus also applies to distros based on debian).

-nixOS: nice concept, i like it, but it being so special means that using stuff precompiled is hard, and will more often than not require special handling. and some stuff is plain broken or doesnt work right.

- gentoo: compiling is slow, and having to deal with circular dependencies makes me want to slice my wrists, pull out my veins, and hang myself with them.

and that brings me to arch. it's ok, but what annoys me of it is that there's no way to automatically install optional packages. So, if a package i need has like a lot of deps (like wine) i need to stare at text, highlight, then press the middle mouse button to paste it to then install such things. I'm working on fixing that for myself though.
And it also has its pros: writing PKGBUILDS is easy, no need for esoteric knowledge or wondering that stuff does on rpm.spec files (%cmake? WHAT DOES IT DO, WILL IT DO WHAT I NEED I DONT KNOW).

I might sound very retarded, and my issues arent that complex, but I want to easily be able to get packages on my system, and if they arent available i want to easily make a package for them. I also want to avoid flatpak for the time being due to it just not being ready yet. (i hope it will someone day be, but until that day comes, arch is the best option for me).