Is it though? I think the first steps are rather easy and then the learning curve goes up dramatically. But it’s not really harder than a manual Arch installation.
i think it depends on what you’re doing, maybe. like I set up sops-nix to manage my secrets, but I wanted to use a Yubikey to protect the master key, so I had to use age-plugin-yubikey… only to discover that sops-nix ignores environment.SOPS_AGE_KEY_CMD for some reason, so I had to point at a random PR on sops-nix to enable experimental plugin support, or dig in and override the sops pkg. then I ran into issues where (I think?) wireguard was coming up before the sops secrets trigger, and failing because it couldn’t read the private key… and then on my WSL2 environment I have to do even more since I cross-compile age-plugin-yubikey to Windows x64 from inside my NixOS build, but then I had to pin a bunch of cargo packages because the repo didn’t ship with anything pinned… and for SWI-Prolog I had to roll my own system for adding modules to it, since the nixpkgs support for that is hilariously broken and fully recompiles SWI-Prolog from scratch every time… and now I’m thinking of setting up a microvm with Wayland forwarding for tor-browser but I can’t imagine how much harder that will be…
…but also like, I can’t imagine doing all of this by hand ever again. once I get my janky-ass nix config working, it’ll keep working for as long as fetch urls stay green (which is a big issue unfortunately.)
Is it though? I think the first steps are rather easy and then the learning curve goes up dramatically. But it’s not really harder than a manual Arch installation.
i think it depends on what you’re doing, maybe. like I set up sops-nix to manage my secrets, but I wanted to use a Yubikey to protect the master key, so I had to use
age-plugin-yubikey… only to discover that sops-nix ignoresenvironment.SOPS_AGE_KEY_CMDfor some reason, so I had to point at a random PR on sops-nix to enable experimental plugin support, or dig in andoverridethe sops pkg. then I ran into issues where (I think?) wireguard was coming up before the sops secrets trigger, and failing because it couldn’t read the private key… and then on my WSL2 environment I have to do even more since I cross-compileage-plugin-yubikeyto Windows x64 from inside my NixOS build, but then I had to pin a bunch of cargo packages because the repo didn’t ship with anything pinned… and for SWI-Prolog I had to roll my own system for adding modules to it, since the nixpkgs support for that is hilariously broken and fully recompiles SWI-Prolog from scratch every time… and now I’m thinking of setting up a microvm with Wayland forwarding for tor-browser but I can’t imagine how much harder that will be……but also like, I can’t imagine doing all of this by hand ever again. once I get my janky-ass nix config working, it’ll keep working for as long as fetch urls stay green (which is a big issue unfortunately.)