This is my problem, perhaps not with nixpkgs, but nixpkgs:nixos-stable. Throughout history the call to fame for distribution is not all the fancy bells and whistles, but the cohesiveness and stability of the stack - the entire stack.
I’m not saying this is a flaw of nixpkgs, but rather a fair amount of technical debt on the of part NixOS maintainers and developers. It’s a vast movable system of modules, while being immutable at the same time. It ain’t easy. So more contribution is needed.
I’m happy that people join and help with that. I’ll still use NixOS and nixpkgs for embedded, specialised cases, even as servers, but I’m not going to run it on a workstation. But, I’m hopeful for the future. I’d like to run it, but not yet.
It’s not really necessary anyways, nix can run on any system… now onto my adventures of bringing nix to an immutable Fedora system without a container or VM lol
This is my problem, perhaps not with nixpkgs, but nixpkgs:nixos-stable. Throughout history the call to fame for distribution is not all the fancy bells and whistles, but the cohesiveness and stability of the stack - the entire stack.
I’m not saying this is a flaw of nixpkgs, but rather a fair amount of technical debt on the of part NixOS maintainers and developers. It’s a vast movable system of modules, while being immutable at the same time. It ain’t easy. So more contribution is needed.
I’m happy that people join and help with that. I’ll still use NixOS and nixpkgs for embedded, specialised cases, even as servers, but I’m not going to run it on a workstation. But, I’m hopeful for the future. I’d like to run it, but not yet.
It’s not really necessary anyways, nix can run on any system… now onto my adventures of bringing nix to an immutable Fedora system without a container or VM lol