unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Blake Shaw <blake@sweatshoppe.org>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile Steel: a proposal for a systems lisp
Date: Sun, 10 Jul 2022 09:46:25 +0000	[thread overview]
Message-ID: <CAKjmbcCbmVKoufu_OmDQJw+xS71S3qoqjan1dbHnbVNUqhw=7Q@mail.gmail.com> (raw)
In-Reply-To: <87v8s6xpnq.fsf@dustycloud.org>

The name is gold (well, actually Steel, but...)

I love the idea as I'd love to be able to do systems programming in Scheme.

I've actually been playing with Loko scheme lately which is really cool and
designed for bare metal.
There are some really cool things going on there, such as Valand, an
experimental wayland-like
compositor written purely in Scheme (see the dev branch if you're
interested). But its still garbage
collected.

Another cool example of what maybe counts as a systems lisp/scheme is the
xtlang from extempore,
designed to allow for the low-level bit fiddling and performance
requirements of per-sample DSP.

If this initiative takes off I'd like to offer my help however I could
contribute :)

---
Blake Shaw
Director, SWEATSHOPPE
sweatshoppe.org
---


On Sat, Jul 9, 2022 at 3:38 PM Christine Lemmer-Webber <
cwebber@dustycloud.org> wrote:
>
> A little blogpost this morning, not actual software, but software
> desiderata:
>   https://dustycloud.org/blog/guile-steel-proposal/
>
> I'd love to see something like the above happen.  I'd love to help make
> it happen.  So this is more of a call to arms than anything else.
>
> Can we have a "systems lisp"?  Can we do better than Rust?  Let's put
> some interesting things on that compiler tower of ours!
>


  reply	other threads:[~2022-07-10  9:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 15:35 Guile Steel: a proposal for a systems lisp Christine Lemmer-Webber
2022-07-10  9:46 ` Blake Shaw [this message]
2022-07-10 12:14 ` Zelphir Kaltstahl
2022-07-11 11:13 ` Tim Van den Langenbergh
2022-07-15 12:08   ` Christine Lemmer-Webber
2022-08-06 22:38     ` Christine Lemmer-Webber
2022-07-11 13:10 ` Martin Becze
2022-08-07  9:28 ` Damien Mattei
2022-08-07 12:43   ` Christine Lemmer-Webber
2022-08-07 14:47     ` Damien Mattei
2022-08-07 16:02       ` Andrew Gwozdziewycz
2022-08-07 20:17       ` Christine Lemmer-Webber
2022-08-07 21:12         ` Damien Mattei

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKjmbcCbmVKoufu_OmDQJw+xS71S3qoqjan1dbHnbVNUqhw=7Q@mail.gmail.com' \
    --to=blake@sweatshoppe.org \
    --cc=cwebber@dustycloud.org \
    --cc=guile-user@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).