zlacker

There are too many stakeholders, it’s too forkable (guix, flox, Anduril).

Maybe the official leadership has a shuffle, maybe it’s even big.

I’m not changing my Nix investment, I discourage others from changing theirs.

>>benree+(OP)
Me neither. Mocking Nix is the new mocking "I use Arch BTW" but when you're deep in it you realize it absolutely is the way, and if it's not Nix or Nix in some more evolved form it will be something very close to it.

>>benree+(OP)
What does guix have to do with Nix (genuine question, not snarky)?

>>slekke+h1
Guix was based on Nix.

>>slekke+h1
It's a bit hidden in their about page:

    GNU Guix provides state-of-the-art package management features such as transactional upgrades and roll-backs, reproducible build environments, unprivileged package management, and per-user profiles. It uses low-level mechanisms from the Nix package manager, but packages are defined as native Guile modules, using extensions to the Scheme language—which makes it nicely hackable.

https://guix.gnu.org/en/about/

>>slekke+h1
same idea, but in a scheme.

>>ddella+W1
If I understand correctly, they're saying that the low level stuff works the way it works in Nix, not that they use Nix for that.

I am aware Guix did fork Nix but from what I've read, there's almost nothing left in Guix that still uses the initial Nix code?

>>brabel+Jh
I am extremely out of the loop, but I believe until somewhat recently it still used nix-daemon and the corresponding drv format, but it may have since been rewritten.