unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Yasuaki Kudo <yasu@yasuaki.com>
To: divoplade <d@divoplade.fr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Mixed Languages Programming
Date: Thu, 11 Mar 2021 22:35:59 +0900	[thread overview]
Message-ID: <BD23B4F5-2CA9-4CAD-A41A-3A11D2B70864@yasuaki.com> (raw)
In-Reply-To: <8d77b850816a9d0d2bd4f244a994d832fd7c32d2.camel@divoplade.fr>

Thank you both,

It feels like using the web API as the interface between the languages would be the simplest.

Guix might come in really handy if the web services are all running on the same Guix machine in which they can share the resources of the OS such as the file system.

Then, using RAM-based or the real disk, different processes compiled in different languages can efficiently exchange data!

That's something that Guix and Nix can do more easily than using Docker web services on other OSes? 😄

Yasu




> On Mar 11, 2021, at 09:00, divoplade <d@divoplade.fr> wrote:
> 
> Hello,
> 
>> Le jeudi 11 mars 2021 à 08:23 +0900, Yasuaki Kudo a écrit :
>> Does anyone have an insight into mixing different programming
>> language?  Say Visual Basic, Java, Racket, Haskell, etc
> 
> I am aware of 3 different kinds of approaches:
> - writing programs in different languages, with one programming
> language occupying a whole process (so, web services as you say, or
> scripts, or an org-mode file, for instance);
> - extending a "managed" programming language with C or C++ code; in
> theory it could be possible to do the same for two different
> programming languages and link both C interfaces together; this is what
> SWIG (http://swig.org/) does, but using some language in another
> language that way feels a lot like coding in C;
> - using a common virtual machine as the target for the compilation of
> many different languages (like elisp and scheme for guile).
> 


      reply	other threads:[~2021-03-11 14:05 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
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 [this message]

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=BD23B4F5-2CA9-4CAD-A41A-3A11D2B70864@yasuaki.com \
    --to=yasu@yasuaki.com \
    --cc=d@divoplade.fr \
    --cc=help-guix@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.
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).