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.
However, Plunder is only tangentially related to Urbit.
It's the same paradigm, but totally different otherwise. Heavy Haskell influence.
The project is still mostly underground, but I'm happy to answer any questions.
It's interesting. Not something I think will affect my day to day life, but in a thought-experiment, LISP-y sort of way I can see why a certain kind of coder might find such a system intriguing. I imagine such a coder is probably into language design, lambda calculus, functional purity and formal verification rather than being on the 'just get things done' end of the spectrum.
I also don't think I can see such a design ever doing anything very quickly, as every operation is necessarily committed to disk. I guess that's where Jets come in...
It's amusing to contrast this with the general mood in programming where we strive to make programs ephemeral so that we don't care what's in memory, things die often and we just re-start them when we feel like it, allowing them to rebuild their internal state.
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 the system is finished, building a full p2p chat should be possible in a couple hundred LOC.
The goal is somewhat political, to enable people to build their own social software, instead of depending on finance for everything.
> I also don't think I can see such a design ever doing anything very quickly, as every operation is necessarily committed to disk.
There is overhead to be sure, but it's nowhere near as bad as it sounds.
In practice, we don't need to fsync every input. Each syscall chooses if it should wait for a sync before running effect. Sync only blocks that effect, everything else continues to run.
For example most REPL IO doesn't need to wait for a sync, but a network transaction does.
P2P chat doesn’t seem like a very lofty goal at this point.
I’m sure there’s a lot more to your platform than PLAN, providing all sorts of facilities, but at that point you’ve kinda scuppered the “execute anywhere, forever” aspect of your model IMHO, because it relies on quite a complex VM to provide the simple coding environment.
Best of luck to you, but I’m still thinking “nerd trap” rather than “revolutionary tech”.
"A lisp machine with fully automatic persistence. No database or filesystem needed" is actually a fairly accurate description.