unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Brett Gilio <brettg@posteo.net>
Cc: Guix Devel <guix-devel@gnu.org>,
	leo.prikler@student.tugraz.at, Amin Bandali <bandali@gnu.org>
Subject: Re: [Proposal] The Formal Methods in GNU Guix Working Group
Date: Mon, 16 Dec 2019 20:46:28 +0100	[thread overview]
Message-ID: <CAJ3okZ3do77KLiNmJC4b_nO19giz4arGTdZ09tdjZ=fqmLCGvQ@mail.gmail.com> (raw)
In-Reply-To: <87tv616q5s.fsf@posteo.net>

Hi,

I am not a Programming Language Theory guy so I speak as a pure noob. :-)
Well, I am working in University Paris 7 Diderot doing some scientific
computing.


On Mon, 16 Dec 2019 at 02:00, Brett Gilio <brettg@posteo.net> wrote:

> so this could be more of a chance to see bigger institutions begin to
> adopt Guix for their research work.

IMHO, today the "win" is not about bootstrapping because it is
strongly language dependent but this "win" offered by Guix is about
the time-traveling reproducibility tools: today the key point in
scientific research (IMHO).
And yes, the reproducibility over the time means bootstrappability.
But it is each scientific community that must take care of its
outputs.

The wider adoption could come from features as "time-machine",
available packages (channels for the not GNU compliant), easy to
distribute, to reproduce, be able to search in all the packages over
all the Guix history, etc.

And what I see as a blocking wider adoption by the Researcher around
me is: Mac. A lot of them just use Mac, I mean they develop daily on
MacOS and then once it is ready run on linux HPC clusters.

I know the article by Ludo and Ricardo. :-) And I strongly agree.
From my point of view, the only way to attract more researchers is to
have an half-baked Guix working on Mac, IMHO.


> -- A lot of proof assistants are based on dialects of ML. Most of these
>    use SMLnj or MLton for their work. To date there is an issue of
>    source-based bootstrapping of _all_ of the major ML compilers. We do
>    have PolyML in our repositories, but even this uses space-inefficient
>    text file blobs for compiling and is not a fully C-based source
>    bootstrap. Basically, all of the ML compilers rely on some distinct
>    pre-compiled something-or-other to get to their pristine state. I
>    have explored the idea, along with Leo and Amin, about following in
>    the tradition of MES (and mrustc) and starting an analogous GNU project for
>    writing a reduced-size specification ML bootstrapping compiler. That
>    way we can end the loop of a source-based build of ML97 compilers
>    being basically impossible.
>    [See issues #38605 & #38606 on DEBBUGS. Also, see
>    https://github.com/MLton/mlton/issues/350.]

It is a ambitious research project. Woow! Nice!! :-)

CakeML [1] claims to be a subset of Standard ML and to be
boostrappable. I do not know enough to have an relevant opinion.

[1] https://cakeml.org/

What is the status of OCaml about boostrappability?


> -- Begin giving talks on the benefits of GNU Guix at conferences around
>    Homotopy Type Theory, Coq, Formal Verification, Deepspec, etc.

Yes, let spread the world! :-)

And IMO a good start is to show in scientific communities why
boostrappability matters.

For example, the papers which were OK in [2] (2015), are they still OK
in 2019? I bet that a lot of big binary blobs have disappear since
then.

[2] http://repeatability.cs.arizona.edu/



All the best,
simon

  parent reply	other threads:[~2019-12-16 19:46 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16  0:59 [Proposal] The Formal Methods in GNU Guix Working Group Brett Gilio
2019-12-16  8:47 ` Julien Lepiller
2019-12-16  9:22   ` Julien Lepiller
2019-12-17  3:29     ` Brett Gilio
2019-12-27 18:56     ` Ludovic Courtès
2019-12-27 22:33       ` Brett Gilio
2019-12-27 23:37         ` Ludovic Courtès
2019-12-28  2:59           ` Brett Gilio
2019-12-30 21:34             ` Ludovic Courtès
2019-12-31 10:17               ` Brett Gilio
2020-01-02 22:11                 ` Ludovic Courtès
2020-01-03 23:49                   ` Amin Bandali
2020-01-15 21:59                     ` Ludovic Courtès
2020-01-13 19:27                   ` Maxim Cournoyer
2019-12-28  7:20           ` Amin Bandali
2019-12-28 11:28             ` Vicente Eduardo
2019-12-29  8:09               ` Jan Nieuwenhuizen
2019-12-17  3:27   ` Brett Gilio
2019-12-16 19:46 ` zimoun [this message]
2019-12-16 20:10   ` Julien Lepiller
2019-12-17  3:40     ` Brett Gilio
2019-12-27 23:56     ` Ludovic Courtès
2019-12-28  2:55       ` Brett Gilio
2019-12-17  3:38   ` Brett Gilio
2019-12-16 23:04 ` Jack Hill
2019-12-17  1:33   ` John Soo
2019-12-17  3:49     ` Brett Gilio
2019-12-17  3:48   ` Brett Gilio
2019-12-21  6:48 ` Amin Bandali
2019-12-21 23:59   ` Brett Gilio
2019-12-28  0:02     ` Ludovic Courtès
2019-12-27 23:54 ` Ludovic Courtès
2019-12-28  3:06   ` Brett Gilio
  -- strict thread matches above, loose matches on Subject: below --
2020-01-23 19:17 Alexandru-Sergiu Marton
2020-02-12 12:02 Orians, Jeremiah (DTMB)
2020-02-12 14:16 ` zimoun
2020-02-12 14:38   ` Svante Signell
2020-02-12 14:48     ` Jan Nieuwenhuizen
2020-02-12 20:59   ` Bengt Richter
2020-02-13 12:13     ` Orians, Jeremiah (DTMB)
2020-02-13 12:07   ` Orians, Jeremiah (DTMB)
2020-02-15 16:10     ` zimoun
2020-02-18 11:17       ` Orians, Jeremiah (DTMB)
2020-02-21 14:47         ` zimoun

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='CAJ3okZ3do77KLiNmJC4b_nO19giz4arGTdZ09tdjZ=fqmLCGvQ@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=bandali@gnu.org \
    --cc=brettg@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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).