All the power to you! For me personally, what I’ve learned in the past few years of using Linux, is that installing things is just half the battle. The other half is discovering them and deciding whether they are worth the time and effort. And I found out about so many useful tools from the Fedora and Bazzite teams that I decided I’d rather let them make the choices for me. Things like pipewire, wayland, fzf, ptyxis, btrfs, podman, distrobox, bazaar, and so much more.
When I want to configure a declarative environment like people do on Nixos, I just use a container, devpod, or distrobox. These are all included on Bazzite DX. But for the base system I prefer to delegate trust to others to save me the time and energy. The maintainers test each tool, and make sure they are stable and work with the rest of the system, so that I don’t have to. And in the future if I decide I don’t like the direction that Bazzite is going, the rpm-ostree rebase system lets me use a single command to switch to a different distro maintained by a different team.
Though to be honest, I wouldn’t be surprised if Nixos had a similar system, and if they don’t right now they probably will in the future. Things are changing fast!
great read, though I still prefer css-in-js. Tailwind still uses css rules and syntax, and I find it clunky when trying to handle complex styling logic.