isakBSD@lemmy.ml to Linux@lemmy.ml · 10 hours ago[From Portuguese to English] Are you ready to embrace Void Linux?felaktig.infoexternal-linkmessage-square2linkfedilinkarrow-up114arrow-down10
arrow-up114arrow-down1external-link[From Portuguese to English] Are you ready to embrace Void Linux?felaktig.infoisakBSD@lemmy.ml to Linux@lemmy.ml · 10 hours agomessage-square2linkfedilink
minus-squaredwt@feddit.orglinkfedilinkDeutscharrow-up1·5 hours agoWhy would I prefer this, if I can get more packages with something like nix - which also works everywhere, but I get reproducibility and gitops on top?
minus-squareisakBSD@lemmy.mlOPlinkfedilinkarrow-up9arrow-down2·4 hours agoChoose Nix if: Reproducibility is critical (dev → prod same environment) You want a GitOps workflow (config as code, versioned) Rollbacks on failure matter (atomic updates) Choose Void if: You want to learn traditional Linux without abstractions Fast package management and lightweight system are priorities Systemd avoidance is a goal in itself Void is a better Linux distro. Nix is a better infrastructure tool. They solve different problems. You were right from the start – if reproducibility and GitOps count, Nix is the only option. Void can’t deliver that.
Why would I prefer this, if I can get more packages with something like nix - which also works everywhere, but I get reproducibility and gitops on top?
Choose Nix if:
Reproducibility is critical (dev → prod same environment)
You want a GitOps workflow (config as code, versioned)
Rollbacks on failure matter (atomic updates)
Choose Void if:
You want to learn traditional Linux without abstractions
Fast package management and lightweight system are priorities
Systemd avoidance is a goal in itself
Void is a better Linux distro. Nix is a better infrastructure tool. They solve different problems.
You were right from the start – if reproducibility and GitOps count, Nix is the only option. Void can’t deliver that.