unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed

From: zimoun <zimon.toutoune@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Advantages over Nix?
Date: Tue, 27 Oct 2020 14:14:18 +0100	[thread overview]
Message-ID: <CAJ3okZ1MMoSbHA5r3NYQReXasT--9Fk2o6mw3t4tfSm43rW1SQ@mail.gmail.com> (raw)
In-Reply-To: <20201027103520.gz53vlymc5nazzby@thebird.nl>

Hey,

On Tue, 27 Oct 2020 at 11:36, Pjotr Prins <pjotr.public12@thebird.nl> wrote:

> Quite a few of us here have used and developed against Nix in the past
> and Nix certainly is a great work and the original inspiration of GNU
> Guix (and doing things better). When Ludo introduced Guix at FOSDEM in
> 2014, however, I was convinced to change my ways on the spot - after
> using Nix (from the early days).  This article is from 2008

About history, couple of days ago I went to [1] from this thread:

https://lists.gnu.org/archive/html/gnu-system-discuss/2012-11/msg00000.html

1: <https://guix.gnu.org/guix-ghm-20120721.pdf>

p.100: Scheme
 - supports embedded DSLs via macro
 - can be used both for composition *and* build scripts

Well, in summary Nix provides the initial "weird paths" and Guix adds
with consistency all the powerful "parenthesis" around. :-)


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.


All the best,
simon

next prev parent reply	other threads:[~2020-10-27 13:14 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 [this message]
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=CAJ3okZ1MMoSbHA5r3NYQReXasT--9Fk2o6mw3t4tfSm43rW1SQ@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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

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).