unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: raingloom <raingloom@riseup.net>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Mixed Languages Programming
Date: Sun, 14 Mar 2021 00:59:57 +0100	[thread overview]
Message-ID: <20210314005957.77361adc@riseup.net> (raw)
In-Reply-To: <d2a9b6e5f7a5f29e64abe67480c1fe87138c1480.camel@zaclys.net>

On Thu, 11 Mar 2021 00:26:41 +0100
Léo Le Bouter <lle-bout@zaclys.net> wrote:

> On Thu, 2021-03-11 at 08:23 +0900, Yasuaki Kudo wrote:
> > Hello!  
> 
> Hello!
> 
> I think you can use JSON-RPC libraries as modern alternatives to that.
> Also gRPC. The "micro-service" paradigm.
> 
> > Is this a topic that is particularly interesting to the Guix
> > community because of interoperability, mixing packages, etc? 😄  
> 
> I don't think so, not in particular.
> 
> > Cheers,
> > Yasu  
> 
> Léo

There is an interesting Nix based project that has some actual good use
cases for a common intermediate representation:
https://publish.illinois.edu/allvm-project/

Chris Webber's talk on Spritely also had some good ideas for using OCAP
in Guix to enhance security by a whole lot.
https://fosdem.org/2021/schedule/event/spritelygoblins/
And that is basically just cross-language remote procedure calls.

Another interesting possibility is to run everything on WASM without an
MMU. See the classic The Birth and Death of Javascript talk.
https://www.destroyallsoftware.com/talks/the-birth-and-death-of-javascript
Of course that one is pre-Spectre/Meltdown, so take it with a grain of
salt.


  reply	other threads:[~2021-03-14  1:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 23:23 Mixed Languages Programming Yasuaki Kudo
2021-03-10 23:26 ` Léo Le Bouter
2021-03-13 23:59   ` raingloom [this message]
2021-03-18 12:34     ` Yasuaki Kudo
2021-03-19  1:20       ` raingloom
2021-03-11  0:00 ` divoplade
2021-03-11 13:35   ` Yasuaki Kudo

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=20210314005957.77361adc@riseup.net \
    --to=raingloom@riseup.net \
    --cc=help-guix@gnu.org \
    --cc=lle-bout@zaclys.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.
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).