all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Lightning talk at IPFS camp
Date: Fri, 07 Jun 2019 22:10:27 +0200	[thread overview]
Message-ID: <87d0jpb1ho.fsf@gnu.org> (raw)
In-Reply-To: <m1k1dx5wx2.fsf@fastmail.net> (Konrad Hinsen's message of "Fri, 07 Jun 2019 15:48:09 +0200")

Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> (They could have chosen Guile instead of a custom Lisp, but that’s an
>> “implementation detail”.  :-))
>
> From my reading of the whitepaper, no. They have pretty strict
> constraints on their language because they send live code updates
> to running instances and want to be able to make certain guarantees.
> Guile, or any other Scheme, would be too flexible.

Oh right, I had overlooked that aspect of the project.  Interesting!

Ludo’.

  reply	other threads:[~2019-06-07 20:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  7:07 Lightning talk at IPFS camp Pierre Neidhardt
2019-05-31 22:10 ` Ludovic Courtès
2019-06-03 15:15 ` Konrad Hinsen
2019-06-03 16:19   ` Pronaip
2019-06-03 18:53     ` Konrad Hinsen
2019-06-06  8:13       ` Pierre Neidhardt
2019-06-06 12:15         ` Konrad Hinsen
2019-06-06 12:36           ` Pierre Neidhardt
2019-06-06 16:53             ` Konrad Hinsen
2019-06-07 12:39             ` Ludovic Courtès
2019-06-07 13:48               ` Konrad Hinsen
2019-06-07 20:10                 ` Ludovic Courtès [this message]
2019-06-07 12:41             ` Ludovic Courtès
2019-06-07 13:45               ` Konrad Hinsen
2019-06-13 21:38         ` ng0
2019-06-24 20:37 ` Pierre Neidhardt
2019-06-26 12:19   ` Pierre Neidhardt
2019-06-27 14:53   ` Ludovic Courtès
2019-06-27 22:04     ` Pierre Neidhardt
2019-07-01 10:16       ` Ludovic Courtès

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=87d0jpb1ho.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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.