all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Tobias Geerinckx-Rice
	<somebody@not-sent-or-endorsed-by.tobias.gr>,
	Guix-devel <Guix-devel@gnu.org>
Subject: Re: Guix pronunciation
Date: Wed, 13 Mar 2019 15:10:46 +0100	[thread overview]
Message-ID: <87y35i7tll.fsf@gnu.org> (raw)
In-Reply-To: <CAPNLzUOCcU5zkAYWUsSAwm3cQcOFFQpvq1EsZaAjFuNPhWU-JA@mail.gmail.com> (Laura Lazzati's message of "Tue, 12 Mar 2019 10:05:23 -0300")

Hi Laura,

Laura Lazzati <laura.lazzati.15@gmail.com> skribis:

>> As for those wondering why: “Guix” is initially just the contraction of
>> Guile + Nix.
> Thank you for the explanation. The person I met interested in at least
> playing whith Guix told me that was thinking of both Guix and Nix, and
> I was asked before about the differences. Is it in the manual? Because
> I don't remember reading it.  Maybe it could be added, before the
> pronunciation, WDYT?

Nix and Guix have technical similarities, in the same sense that Debian
and Fedora have technical similarities, but the projects have different
goals, priorities, commitments, and processes.  Guix is committed to
user freedom and to building software from source, for instance.

Nix and Guix have also significant technical differences arising from
the use, in Guix, of a single general-purpose language for everything,
with embedded domain-specific languages (EDSLs) as needed.  That, in
turn, makes the system very hackable and extensible, and that’s what
makes it easy to write several UIs (CLI, Emacs, web), simple UIs, new
tools around Guix like ‘guix pack’ or the Guix Workflow Language, etc.

I wrote about the initial vision regarding the programming language
approach in <https://arxiv.org/pdf/1305.4584.pdf>.  Ricardo wrote a more
up-to-date and more comprehensive answer on HN:
<https://news.ycombinator.com/item?id=18910683>.

Should we write this more prominently somewhere?  Probably!  :-)

Ludo’.

  parent reply	other threads:[~2019-03-13 14:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-10 16:13 Guix pronunciation mikadoZero
2019-03-10 17:20 ` Tobias Geerinckx-Rice
2019-03-11  2:45   ` mikadoZero
2019-03-11 22:32     ` George Clemmer
2019-03-10 17:21 ` Tobias Geerinckx-Rice
2019-03-12 12:48   ` Ludovic Courtès
2019-03-12 13:05     ` Laura Lazzati
2019-03-12 13:12       ` Pierre Neidhardt
2019-03-12 13:21         ` Laura Lazzati
2019-03-13 14:10       ` Ludovic Courtès [this message]
2019-03-13 15:08         ` Laura Lazzati
2019-03-15  1:10       ` mikadoZero
2019-03-10 17:51 ` sirgazil
2019-03-11  1:43   ` mikadoZero
2019-03-11 21:26   ` Laura Lazzati
2019-03-11 21:06 ` L p R n d n
2019-03-11 23:51 ` Leo Famulari
2019-03-12  4:52 ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y35i7tll.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=Guix-devel@gnu.org \
    --cc=laura.lazzati.15@gmail.com \
    --cc=somebody@not-sent-or-endorsed-by.tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.