unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Idea: a meta language for (language) build systems - npm, Racket, Rust cargo
Date: Tue, 01 Jun 2021 09:56:34 +0200	[thread overview]
Message-ID: <m1lf7uxbkd.fsf@fastmail.net> (raw)
In-Reply-To: <20210531174748.mhaelcqwmo7degfc@thebird.nl>

Hi Pjotr,

> I have a feeling they won't be that interested ;).

Depends on who and when. My idea is not to send them a mail saying,
"look, we have a great idea, you should us it!". It's rather to open
issues on their build systems to suggest features and actually help with
the implementations. Good old proselytism ;-) It's a long-term strategy,
not a quick fix project.

> Industry appears to go the other way. There are several initiatives to
> speed up Rust through caching and storing compiled items in the
> cloud(?!).

Then it's time to intervene before it's too late ;-)

There is a clear momentum building up for reproducibility. Few people
argue nowadays that it doesn't matter. It's more like "would be nice,
but it's too difficult/complicated". That's where Guix can help: as a
demonstration of possibility. And once your builds are reproducible,
you can safely cache them in the cloud!

The next message to get across is the need for cross-language build
systems. The idea of one language, one platform doesn't work any more.
Real software systems need to mix languages, even runtimes. And it's not
just X + C any more either. Again, Guix serves as the proof of concept,
even for people who dislike some specific implementation aspect of Guix.

Cheers,
  Konrad.


  parent reply	other threads:[~2021-06-01  7:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30  8:38 Idea: a meta language for (language) build systems - npm, Racket, Rust cargo Pjotr Prins
2021-05-30 19:17 ` Konrad Hinsen
2021-05-31 17:47   ` Pjotr Prins
2021-06-01  5:50     ` Adriano Peluso
2021-06-01  6:24     ` Leo Prikler
2021-06-01  7:23       ` Pjotr Prins
2021-06-01  8:12         ` Leo Prikler
2021-06-01  8:59       ` Adriano Peluso
2021-06-01  9:11         ` Leo Prikler
2021-06-01 10:52           ` Adriano Peluso
2021-06-01 11:03             ` Leo Prikler
2021-06-01 11:28               ` Adriano Peluso
2021-06-01 15:22                 ` Leo Prikler
2021-06-01  7:56     ` Konrad Hinsen [this message]
2021-06-01 23:35       ` Joshua Branson
2021-06-08 13:11     ` Ludovic Courtès
2021-06-14 14:29       ` Pjotr Prins
2021-06-14 22:04         ` Leo Prikler
2021-06-15  8:48           ` Pjotr Prins
2021-06-15 10:08           ` Ricardo Wurmus
2021-06-20 15:46         ` 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

  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=m1lf7uxbkd.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --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
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).