4 ms·
Interesting! I don't think I quite understand how this compares to the vat model of actors that was used in E and what tuplespaces are contributing here. I gues
by davexunit 2y ago
Interesting! I don't think I quite understand how this compares to the vat model of actors that was used in E and what tuplespaces are contributing here. I guess I'd just need to sit down and try using the language.
See also Goblins, an actor model + object capability system inspired by a lot of the same stuff (like E) that uses the Preserves-derived Syrup format for encoding messages over the network. https://spritely.institute/goblins/ https://spritely.institute/goblins/
There's also a standard in development for communicating capabilities over the network called OCapN: https://ocapn.org/ https://ocapn.org/
- dannyobrien 2y agoI think there's some pre-existing crossover with the projects (e.g. Spritely/Ocapn's Syrup serialisation format is a version of Syndicate's Preserves) https://preserves.dev/ https://preserves.dev/ https://gitlab.com/spritely/syrup https://gitlab.com/spritely/syrup