Email or username:

Password:

Forgot your password?
Top-level
nmeum

@civodul Having experimented with both Nix and Guix recently, I personally feel like Guix is more approachable because it uses a Scheme EDSL instead of inventing its own language. However, I also had prior experience with Scheme which likely gave me a head start on Guix. Probably hard to come up with an “objective answer” though…

3 comments
Justin

@nmeum @civodul

I've also had a better time learning Guix.

I think Guix is more approachable than Nix - not only because it's based on a programming language with simpler semantics - but because they've put more time into their documentation and included more tools into into the default ecosystem. IE `guix home`.

Justin

@nmeum @civodul

However, I feel that Nix has focused on meeting the developer where they are at. We can see this because I think they differ in the developer experience in two important ways. They've leaned heavily into `devShells` with having various shell hooks and being able to set environment variables. And they support a wider array of systems. I like working on MacOS, so being able to use Nix to _easily_ manage my dev environments is what ultimately made me side with Nix.

Justin

@nmeum @civodul

The devShell enhancements might exist in Guix; I just never found it when I was playing with it.

The other thing that I think Guix could beat Nix is autocomplete. I think Guix could more easily support systems like LSP, making writing these systems much easier.

Go Up