unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Guix Without Scheme
Date: Wed, 20 Jul 2022 17:45:51 +0200	[thread overview]
Message-ID: <87v8rrn5ie.fsf@riseup.net> (raw)
In-Reply-To: <20220720005325.GB24891@gac>


jgart <jgart@dismail.de> writes:

> Hi Guixers,
>
> I just wanted to share this presentation that Singpolyma gave titled "Guix Without Scheme":
>
> https://archive.org/details/singpolyma-guix-without-scheme
>
> Through the course of the presentation, singpolyma demos how to build
> a Guix package with javascript as well as lua.
>
> What do people think of leveraging Guile's compiler tower to write Guix
> packages in lua, javascript, python, and other languages? 
>
> nix perhaps? Might be meta fun to write a Guix package in a guile implemented nix frontend.
>
> Maybe we should think of Scheme as just one frontend among many to Guile's compiler tower?
>
> Is it a future goal for Guix to fully support this unique feature?
>
> all best,
>
> jgart

I like Lua but this doesn't seem to be a wise use of developer
resources.  Those languages have subtle differences that would surface
if this idea was pursued further.  The most obvious one: Scheme is very
permissive with what you can name your variables, while all the others
basically follow C's restrictions.  How would you map those names?  It
is not possible to create a bijection between sets of different
cardinality.  And then we haven't gotten into how the module systems are
different or how record systems aren't even standardized among Schemes.

If you want to experiment with mixing languages, Racket is likely a
better starting point.


  reply	other threads:[~2022-07-20 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20  5:53 Guix Without Scheme jgart
2022-07-20 15:45 ` Csepp [this message]
2022-07-20 21:02   ` Munyoki Kilyungi
2022-07-21 10:23     ` Csepp

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=87v8rrn5ie.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    /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).