New features include:
For info on how guix-daemon --listen (networked daemon) is used, check out https://guix-hpc.bordeaux.inria.fr/blog/2017/11/installing-guix-on-a-cluster/
I am still a bit confused by the Nix vs. Guix thing. Not that I am against having two similar projects per se, but I don’t know.
Guix took parts of the Nix package manager and retooled them to use Scheme instead of the Nix language. This works because the Nix build process is based off a representation of the build instructions (“derivations”) and has nothing to do with the Nix language. Guix is also committed to being fully FOSS, whereas the Nix ecosystem will accept packages for any software we can legally package.
Also there is of course accumulated divergence as people with some particular idea happen to be in the one community and not the other.
Nix has NixOps and Disnix, but there still is no GuixOps.
On the other hand I believe the guix service definitions are richer, and guix has more importers from programming-language-specific package managers, but then on the third hand the tooling for Haskell and Node in particular is better in nix.
Nix supports OSX, FreeBSD and cygwin, guix supports the Hurd.