From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Yasuaki Kudo <yasu@yasuaki.com>, help-guix <help-guix@gnu.org>
Subject: Re: Mixed Languages Programming
Date: Thu, 11 Mar 2021 00:26:41 +0100 [thread overview]
Message-ID: <d2a9b6e5f7a5f29e64abe67480c1fe87138c1480.camel@zaclys.net> (raw)
In-Reply-To: <FFAF4003-70A2-4808-AE32-23D11718F7E6@yasuaki.com>
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-10 23:27 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 [this message]
2021-03-13 23:59 ` raingloom
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=d2a9b6e5f7a5f29e64abe67480c1fe87138c1480.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=help-guix@gnu.org \
--cc=yasu@yasuaki.com \
/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).