From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: guile-user@gnu.org
Subject: Spritely Goblins v0.10 released for both Guile and Racket!
Date: Mon, 30 Jan 2023 16:12:45 -0500 [thread overview]
Message-ID: <87h6w7soug.fsf@dustycloud.org> (raw)
Hey everyone! I'm excited to announce a *huge* release of Goblins!
The whole engineering team (Jessica Tallon, David Thompson, and of
course myself) have been plugging away hard on this release and now
we're thrilled to announce Goblins 0.10 for both Guile and Racket:
https://spritely.institute/news/spritely-goblins-v010-for-guile-and-racket.html
It's already available in Guix!
guix pull
guix install guile-goblins
There's a lot here, I'm going to focus mainly on the Guile version since
this is guile-users:
- Racket and Guile versions of guile-goblins programs can both now
collaborate and communicate seamlessly over the network!
- Live hacking has never been easier with the new ,enter-vat REPL
command!
- You can now plug in your own event loops (GTK, chickadee, etc)!
- Dramatically updated info manual!
- A nice HTML rendering of said manual!
https://spritely.institute/files/docs/guile-goblins/0.10/index.html
And... and... AND!
The Guile version of Goblins is now the OFFICIAL version of Spritely
Goblins! While the Racket version will be continued to be maintained
for interoperability, we made the decision to prioritize the Guile
version as the version we'll be focusing on going forward.
For more about Goblins, read its homepage:
https://spritely.institute/goblins/
Or the Heart of Spritely whitepaper!
https://spritely.institute/static/papers/spritely-core.html
That's all! If you make something cool with Goblins, please let us
know!
- Christine Lemmer-Webber, Spritely Institute CTO
next reply other threads:[~2023-01-30 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 21:12 Christine Lemmer-Webber [this message]
2023-01-30 22:03 ` Spritely Goblins v0.10 released for both Guile and Racket! Dr. Arne Babenhauserheide
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=87h6w7soug.fsf@dustycloud.org \
--to=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).