(which, as far as I can tell, also supports capabilities and caveats for security)
Neat work!
[0] https://syndicate-lang.org/
[1] https://files.spritely.institute/docs/guile-goblins/0.17.0/T...
[2] https://spritely.institute/news/composing-capability-securit...
- the SAM coordinates through the dataspace, whereas Goblins is focused on ("point-to-point") message passing
- SAM (as presented) doesn't contain a transactional semantics -- e.g. turns are atomic, and there's no rollback mechanism (I haven't been up to speed on recent work, I do wonder if this could be designed into SAM)
but I think the difference is the "distributed" part, where I think they mean distributed over untrusted networks as opposed to distributed over nodes in a private cluster
The animation and this statement with clear practical usage got me interested. Is there active work going on in this area? I'd like to see how that interacts.
https://spritely.institute/news/shepherd-goblins-update.html
I think my brain naturally wants to think about things in terms of sending messages between smaller components of a program, so Goblins fits the way I think very well. It's also what introduced me to object-capability security, which is a lot more brain-bendy when you're first trying to understand it, but after a lot of reading and playing with Goblins I find myself wishing many more things used ocaps. :)
