malfisya

We have pretty easy to use homegrown package manager (eopkg). We also have our own software center, though it is in the process of being replaced by Gnome Software and KDE Discover. You can install software from Solus repository or Flathub via those software center. We adopt what we called “curated-rolling” release, we only do software update on Friday. We also ensure that packages from our repositrory can be run OOTB without user configuration, using principle what is called “stateless”. You can find out more about Solus on the website, help center, and forum.

True, I just like start minimal and add on top of that. Truth be told, my experience with Garuda is minimal.

I would guess jumping from PopOS to Bazzite would be a challange becaue of it is immutable base. It is supposedly less prone to brekage, but certain guides won’t work on them.

I think Nobara (or Fedora KDE) will work for you to try. I would avoid Garuda. It has many GUI for helping new user but if learning is your purpose, that just gets in the way. I would suggest Endeavor OS for Arch-based distro.

This is a left field suggestion: Try Solus !solus@piefed.social , we have a pretty good KDE edition. :)

Cheers!

I use this too daily (I am a sucker for looks), but hands down Okular is better.

From what I read Preview is full suite of PDF reader right? If so Okular by KDE seems like a good alternative.

I like game emulation and to manage my ROM library, I use Geode-GEM. It is simple but cusomizable app to manage your ROM based on console and emulator you have.

That is honestly surprising, I thought we were cautious about it at !solus@piefied.social . We already defaulted to Wayland on Plasma and Gnome for about a year (IIRC).

This is an old comment but I am replying anyway.

The idea of statelessness is not limiting user configuration but giving user a sane default config. Many software doesn’t work without a config file, the idea is that a software should ship a default (vendored) configuration that make the software can be used as is. The default config is stored at vendored directory. This default config file then should be able overriden by user own config.

For example: Alex needs program “A” for work but program “A” needs a config file to even launch. Ideally the program “A” should ship a default config file to vendored directory in /usr. If Alex needs to modify the configuration to fit his needs, now he can do that by copying the default configuration in /usr directory to either /etc (system wide) or /.local/config (per-user). Alex now can modify the config file as he pleases. Now, in case some modification Alex made make program “A” doesn’t work, he can just nuke his own config file and program “A” will work again because of the default config is there as a fallback.

Good news is many program is already following this schema of configuration files but there are also many low-level program that does not (bash, pam, etc).