From: ludo@gnu.org (Ludovic Courtès)
To: Amirouche Boubekki <amirouche.boubekki@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Guix world tour
Date: Tue, 04 Oct 2016 10:36:20 +0200 [thread overview]
Message-ID: <87r37wecjf.fsf@gnu.org> (raw)
In-Reply-To: <CAL7_Mo_8EH0P1H3JQvU5-majqrfcx+URSDgcrBXx4zNZf2u+0g@mail.gmail.com> (Amirouche Boubekki's message of "Tue, 04 Oct 2016 07:18:31 +0000")
Hi,
Amirouche Boubekki <amirouche.boubekki@gmail.com> skribis:
> On Fri, Sep 30, 2016 at 11:45 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
>> The CUFP talk was in this very nice room with 60 people or so. I
>> focused on why and how we use Scheme extensively, explicitly comparing
>> to Nix{,OS}, which the majority of the attendance already knew. Among
>> the questions I had, one was “how do I upgrade from Nix?” ;-), and
>> another one was the inevitable (given the venue) “what do you think a
>> static type system would bring you?”.
>>
>
> What is the answer to the last question about static type system?
Heh. :-) There’s a transcript of what I said at
<http://icfp2016.mirage.io/CUFP/guix-scheme-as-a-uniform-os-a.md>.
I think the core of Guix could benefit from it, just like any other
program. The user-facing data structures and procedures
(‘operating-system’, ‘package’, etc.) could be locally statically typed
(for instance, record fields), but not much beyond that because I
suspect this would either hamper dynamic composition or provide a false
sense of static typing.
Ludo’.
next prev parent reply other threads:[~2016-10-04 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 15:54 Guix world tour Ludovic Courtès
2016-08-30 16:06 ` Alex Sassmannshausen
2016-08-30 16:46 ` Andy Wingo
2016-08-31 8:56 ` Ricardo Wurmus
2016-09-30 9:45 ` Ludovic Courtès
2016-09-30 13:02 ` Ricardo Wurmus
2016-10-03 20:46 ` Ludovic Courtès
2016-10-04 7:18 ` Amirouche Boubekki
2016-10-04 8:36 ` Ludovic Courtès [this message]
2016-10-26 9:57 ` 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=87r37wecjf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=amirouche.boubekki@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 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.