No way. It’s still a specialist OS. There’s no way I’m putting this into the hands of a linux newbie or even the average linux user. There config still doesn’t have a UI, the flakes vs non-flakes debate is still in full swing (nixpkgs doesn’t have flakes), the doc is far, far, far from user friendly, writing a nix package is still not easy, and so much more.
Nix for sure was (and probably is) ahead of its time, but the UX is amongst the worst I’ve experienced - and I’ve written init and upstart services and configured my network with ipconfig before networkmanager was stable.
Did you just post a license for your humblebrag soapbox rant about NixOS?
Edit: I’ll leave some points where I agree since you’re very fixated on/preoccupied with who won this debate (or something). In the long run, most Nix users are wishing for a complete rewrite of NixOS with Nix’s modern approach codified as standard. After all, to your point, Nix is just a massive pile of Perl and Bash under the hood. It could unquestionably be more capable if they had the benefit of hindsight (or a proper type system built into the language) like GUIX which uses Scheme as their DSL has. AFAIK, though, Nix flakes are a feature that GUIX badly needs.
For GUIX: Does anyone know about content-addressed derivations in GUIX? I figure that might also be a place where Nix bests GUIX but perhaps some GUIX(pronounced geeks) can correct me before I search for answers.
I don’t really care to be honest. Clearly, I’m not as smart as you and would be in hell with maintaining my version-controlled flake that provisions rock-solid stable nix-configs for 8 different machines on a variety of vastly different architectures if I had your 10x dev brain.
No way. It’s still a specialist OS. There’s no way I’m putting this into the hands of a linux newbie or even the average linux user. There config still doesn’t have a UI, the flakes vs non-flakes debate is still in full swing (nixpkgs doesn’t have flakes), the doc is far, far, far from user friendly, writing a nix package is still not easy, and so much more.
Nix for sure was (and probably is) ahead of its time, but the UX is amongst the worst I’ve experienced - and I’ve written
initandupstartservices and configured my network withipconfigbefore networkmanager was stable.Anti Commercial-AI license
🙄
Did you just post a license for your humblebrag soapbox rant about NixOS?
Edit: I’ll leave some points where I agree since you’re very fixated on/preoccupied with who won this debate (or something). In the long run, most Nix users are wishing for a complete rewrite of NixOS with Nix’s modern approach codified as standard. After all, to your point, Nix is just a massive pile of Perl and Bash under the hood. It could unquestionably be more capable if they had the benefit of hindsight (or a proper type system built into the language) like GUIX which uses Scheme as their DSL has. AFAIK, though, Nix flakes are a feature that GUIX badly needs.
For GUIX: Does anyone know about content-addressed derivations in GUIX? I figure that might also be a place where Nix bests GUIX but perhaps some GUIX(pronounced geeks) can correct me before I search for answers.
Lol, are you unhappy somebody disagrees with you? Quite childish.
Anti Commercial-AI license
I don’t really care to be honest. Clearly, I’m not as smart as you and would be in hell with maintaining my version-controlled flake that provisions rock-solid stable nix-configs for 8 different machines on a variety of vastly different architectures if I had your 10x dev brain.
MIT License