From: Pjotr Prins <pjotr.public12@thebird.nl>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Advantages over Nix?
Date: Wed, 28 Oct 2020 06:58:45 +0100 [thread overview]
Message-ID: <20201028055845.m25ehnm65wvshjbm@thebird.nl> (raw)
In-Reply-To: <CAJ3okZ1MMoSbHA5r3NYQReXasT--9Fk2o6mw3t4tfSm43rW1SQ@mail.gmail.com>
On Tue, Oct 27, 2020 at 02:14:18PM +0100, zimoun wrote:
> Let's pick an example: the sources.json file ingested by Software
> Heritage. Basically, Guix does that when building its website and the
> relevant Scheme code is here:
>
> <https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/tree/website/apps/packages/builder.scm#n96>
>
> Nothing more. Compare to what Nix does:
>
> <https://github.com/nix-community/nixpkgs-swh>
>
> so pieces of Nix DSL which generates files that are parsed by Python
> and then glued with Shell.
Thanks Zimoun. In a nutshell :). I am convinced that the reason that
Guix is moving fast is not that the community consists of a bunch of
geniuses, but that the code base is terse and many people in this
community understand the code base to a large degree quickly and can
contribute. Of course I don't want to downplay genius - some of it
there is in a massive project like this.
I also think that the choice of being a true free software project is
very important. It is a long term force driving the project forward to
a future where we have free hardware and free software as choice for
all things.
We have our first RISCV board up and running, if anyone is
interested...
Pj.
next prev parent reply other threads:[~2020-10-28 5:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 7:42 Advantages over Nix? Taylan Kammer
2020-10-26 9:29 ` 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 [this message]
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=20201028055845.m25ehnm65wvshjbm@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).