From: Taylan Kammer <taylan.kammer@gmail.com>
To: guix-devel@gnu.org
Subject: Advantages over Nix?
Date: Mon, 26 Oct 2020 08:42:34 +0100 [thread overview]
Message-ID: <87blgpl9g5.fsf@gmail.com> (raw)
Hi Guixers,
Personally I'm a GNU-lover and a Scheme-lover so it's obvious why I
would choose Guix over Nix.
However, currently at my workplace I'm trying to pitch Nix/Guix as a
better way of generating Docker container images, opposed to the impure
Dockerfile way of doing it.
(I've never really worked with Docker yet so my understanding is very
shallow; I hope what I'm saying makes sense. My understanding is that
via Dockerfiles you generate images imperatively, and the results are
dependent on the state of the universe. Yuck!)
So now the question is: given that Nix is older and thus probably more
mature, are there any non-subjective, non-ideological reasons to pick
Guix over Nix?
I've never worked with Nix, and neither have I messed with the more
spicy features of Guix yet (like 'guix deploy') so I really have no
idea!
What I've noticed so far though, is that things like "guix pack" and
"guix deploy" are baked right into Guix and very well documented,
whereas Googling how to do equivalent things with Nix seems to often
return results related to extra tools... Am I just bad at looking up
Nix documentation? Currently I have the impression that it would be
much easier to create Docker images with Guix than with Nix! But maybe
that's wrong.
TL;DR: sell Guix (over Nix) to someone who doesn't care about GNU or
Scheme?
- Taylan
next reply other threads:[~2020-10-26 7:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 7:42 Taylan Kammer [this message]
2020-10-26 9:29 ` Advantages over Nix? Jan Nieuwenhuizen
2020-10-26 11:36 ` Taylan Kammer
2020-10-26 23:39 ` Ludovic Courtès
2020-10-27 10:35 ` Pjotr Prins
2020-10-27 13:14 ` zimoun
2020-10-28 5:58 ` Pjotr Prins
2020-10-26 10:41 ` zimoun
2020-10-26 11:44 ` Pierre Neidhardt
2020-10-26 12:46 ` Taylan Kammer
2020-10-26 12:42 ` Taylan Kammer
2020-10-26 16:14 ` zimoun
2020-10-26 20:29 ` Yasuaki Kudo
2020-10-26 22:32 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blgpl9g5.fsf@gmail.com \
--to=taylan.kammer@gmail.com \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).