I use nix today for ci/cd to build a large C++ project for a variety of architectures using cross-compiles. While it could be done with adhoc scripts, some cross compiler tool environment tool + conan, or something else, I effectively wrote my nix expression once to package up everything, and simply changed the target arch and libc and got what I wanted.
It's not perfect, but it works, its fast, and its better than the alternatives.
I'm interested in rying Guix at somepoint instead as I think using Guile might be easier than learning the Nix language, cli tools, and more. I think guix could do much what I do now as well.
I can't see myself using guix as an OS though, since they seem to think systemd is evil or something, and really systemd is quite nice in practice in my experience.
Hey, we're glad to hear you're interested in Guix :)
I just wanted to say that Guix doesn't hate systemd, or think of itself as an anti-systemd project or anything like that.
Systemd was not chosen because GNU already had a (quite simplistic) init system written in Guile Scheme, and we want to use Guile for the entire system.
Eventually, our goal is to offer a fully integrated interface for managing the system, just like systemd. We are not there yet :)
Is it really wise to go against such important/widely-used part of the linux userspace? I do find Guix as cool as NixOS, but this decision seems like a self-inflicted wound.
Nonetheless, I should definitely get to know the project more, because it was some time ago I tried it last.
So, Good luck with the project! :)
It's not perfect, but it works, its fast, and its better than the alternatives.
I'm interested in rying Guix at somepoint instead as I think using Guile might be easier than learning the Nix language, cli tools, and more. I think guix could do much what I do now as well.
I can't see myself using guix as an OS though, since they seem to think systemd is evil or something, and really systemd is quite nice in practice in my experience.