sol_plunder

4 ms·

1.
by sol_plunder 3y ago
That sounds right! I'll keep that in mind. "A lisp machine with fully automatic persistence. No database or filesystem needed" is actually a fairly accurate description.
2.
by sol_plunder 3y ago
Think of it as being a Scheme implementation: Racket, Stalin, Larceny, Plunder.
3.
by sol_plunder 3y ago
The main use-case is for building peer-to-peer systems with small eng resources. The win is basically that the entire stack gets much less complex. Network, database, and business logic all operate within the same model. For example, once
4.
by sol_plunder 3y ago
There is a fair bit of overlap, but Plunder processes are persistent and Erlang processes are ephemeral. Making processes persistent has nontrivial overhead, so the Erlang model probably doesn't translate well in practice to Plunder.
5.
by sol_plunder 3y ago
This document was written by Urbit devs, and for Urbit devs. Plunder is not an obscurantist project, and intends to be straightforward and easy to understand.
6.
by sol_plunder 3y ago
Plunder dev here: Here is a recent attempt to explain the paradigm succinctly: https://git.sr.ht/~plan/plunder/tree/master/item/doc/PLAN.md Very open to feedback as to how to express these idea
7.
by sol_plunder 3y ago
The paradigm is quite difficult to describe well. Another attempt is here: https://git.sr.ht/~plan/plunder/tree/master/item/doc/PLAN.md
8.
by sol_plunder 3y ago
Main Plunder dev here, wasn't expecting to see this here. This document was written by an Urbit dev, and the Urbit community is the target audience. The conversation here seems to be mostly shitting on Urbit with the usual HN critiques