NixOS tends to encourage “proper” solutions instead of hacky temporary solutions, so while doing stuff on NixOS takes more time, maintaining what you’ve done is much easier, and it’s much easier to reason about, so I learned much more on NixOS than I learned on Arch (hell, I wrote two Nix DSLs for nftables and Lua because my perfectionism told me I need to do that instead of manipulating config as strings in Nix). I have an initrd hook that configures GPU passthrough by picking a GRUB option, I have a system configuration for an Arm router SoC (BPI-R3), which is a painful piece of hardware to work with, much like other SoCs, I have the router config itself (which I wrote a Nix framework for) - and if I ever forget how that all works, I can read the config to remember it, instead of trying to figure out what Linux commands I ran “back then”. But if your goal is just learning about Linux, look elsewhere - that was just a bonus for me; Nix is an abstraction, and you can only start learning Linux after you understand that abstraction.