unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Guile User <guile-user@gnu.org>
Subject: [ANN] Spritely Goblins 0.11.0 released!
Date: Mon, 8 May 2023 13:40:47 -0400	[thread overview]
Message-ID: <CAJ=RwfaAajnA-aqJgHAZ-0iNqzujeANGUL5_m+F67SShOtL1fQ@mail.gmail.com> (raw)

Hey Guilers,

The Spritely team is excited to announce Goblins 0.11.0 for Guile!
(And Racket, too, but you're reading guile-user!)

Highlights from this release:

* A new time-traveling distributed debugger
* Substantially improved documentation and docstrings
* Several more actor-lib modules ported from Racket to Guile
* Updates to OCapN (the Object Capabilities Network) code

For more information, including a video demonstration of the new
debugger, check out the release announcement on our blog:

  https://spritely.institute/news/spritely-goblins-v0110-released-time-travel-distributed-debugging-and-more.html

About Goblins:

Spritely Goblins is a distributed object programming environment.
Goblins provides an intuitive security model, automatic local
transactions for locally synchronous operations, and an easy to use
and efficient asynchronous programming interface for encapsulated
objects which can live anywhere on the network. Its networking model
abstracts away these details so the programmer can focus on object
programming rather than protocol architecture.

For more information and download links, check out our project home page:

  https://spritely.institute/goblins/

For more information about our architecture and mission, check out the
Heart of Spritely whitepaper (which has been updated with many helpful
diagrams!):

  https://spritely.institute/static/papers/spritely-core.html

If you make something cool with Goblins, please let us know!

- Dave (on behalf of the entire Spritely team)



                 reply	other threads:[~2023-05-08 17:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJ=RwfaAajnA-aqJgHAZ-0iNqzujeANGUL5_m+F67SShOtL1fQ@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --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).