At my workplace, Guix's lack of macOS support takes away some of the benefit of using something like Nix or Guix as opposed to HVM solutions like Docker Desktop or Vagrant. I imagine this situation is unfortunately common.

For teams where GNU/Linux is the primary development OS, Guix seems like a great choice.

YMMV, I really don't like lisp braces personally.

It's not "the problem", but it's a problem. It's better than alternatives, but it's hacky nature shows.

Well, if you believe:

- discoverability is a problem in Nix

- Guix encourages or "shepherds" more discoverable functions, modules, and abstractions

Then the language could be a problem.

What is?

That's, like, just your opinion, man.

Scheme and/or Lisp is literally the worst language choice for this problem domain.

Why is Lisp the worst for this problem domain?

I will admit I find guix to be much more verbose than Nix.

For starters, a configuration language needs to be lazy by default. (Unless you want to evaluate the whole world every time you change one line.)

I wouldn't say it's the worst. I don't like Lisp and co, but I think it's alright for this. I don't like Guix for a very different reason.