LunchSep 21, 2023

What to distro to hop to next?

https://lemmy.world/post/5463838

What to distro to hop to next? - Lemmy.world

So been trying out Garuda Linux for a while now (my first distro), but feel ready to try another distro. Therefore looking for a distro that suits my preferred requirements, anyone has any tips? > Uses Wayland > Supports flatpak > ButterFS format > KDE Plasma > “Good for gaming” Note: Got nothing negative about Garuda, I just want to explore the options out there :)

Show threadsilencerSep 21, 2023
Arch is great, I’m using Plasma on Wayland and it works really well.
Show threadOcelotSep 21, 2023
Just switch to arch and stop hopping. Literally any feature that might make you want to switch to another distro Arch can do just fine.
Show threadTootGuitarSep 22, 2023
I love Arch but I’d caution you against hyperbole like this. For example, NixOS has a declarative config for the whole system along with atomic builds that can be rolled back or switched dynamically. Not aware of any way to do any of that in Arch.
Show threadOcelotSep 22, 2023
like this? wiki.archlinux.org/title/Nix
Nix - ArchWiki

Show threadTootGuitarSep 22, 2023
No, because while that lets you use nix to manage some of your packages, it’s still fundamentally limited by being hosted within the imperative Arch install. See for example section 2 in the very link you shared, which talks about starting the nix daemon at boot by messing with your systemd config.
Show threadOcelot
how so? what is left after having the system daemon start at boot? this is a super common thing to do. If you wanted to go a step further you could even create a couple chroots or other immutable partitions to swap the bootloader to. This would be a great way to use the package manager and features of nix without the limitations.
Sep 22, 2023 at 1:12amWeb
Show threadTootGuitarSep 22, 2023
You said Arch can do “literally anything” that any other distro could do, and I’m trying to point out that by having to issue imperative command(s) to set Nix up on Arch, you’ve already conceded that the entire state of the system is not able to be declared in a config file, which is one of the features of NixOS. So there is at least one thing that NixOS can do that Arch can’t. I imagine there are other examples (and not only when comparing with NixOS). So again I ask, can you please refrain from hyperbole?