mhuesch

there are pretty few mentions of Urbit in the core Plunder project/codebase & many of the core concepts are different (and more conventional, I might add).

https://sr.ht/~plan/plunder/

    ~/projects/plunder ‹master› » grep -i urbit -r . | wc -l
    5

I've been following along w/ Plunder for the past 10ish months and I essentially "bounced off" of Urbit's (imo) opaque terminology, opting to learn Plunder instead as it seemed much more concise and better conceptually distilled. not knowing Urbit has not been much of a hindrance. so I think the "guilt by association" you are seeing comes more from the framing of the above gist, which was aimed at an Urbit audience & cross-posted to HN by someone not associated w/ Plunder.

Plunder does not use much of Urbit's terminology, outside of the linked gist, which was intended for Urbit devs, and which was cross-posted here by someone from Twitter.

I've been following along w/ Plunder for the past 10ish months out of personal interest, and I find the terminology to be about as straightforward as one can expect for a technical domain which is quite complicated.

perhaps this document is more straightforward? feedback is welcome.

https://git.sr.ht/~plan/plunder/tree/master/item/doc/PLAN.md

sort of, in theory, but in most practical lisp/scheme implementations, certain values are opaque primitives. often functions are opaque. hashmaps, etc, are often primitives which don't have a "dependable formal representation". this means they cannot be e.g. serialized and coherently transmitted between processes.

Urbit solved this with nouns, which is arguably a substantial innovation. PLAN (in the author's view, which I find convincing) improves on this: https://git.sr.ht/~plan/plunder/tree/master/item/doc/PLAN.md