9 ms·
Plunder and Urbit
- vonnik 3y ago> “urbit would win” I wonder what Urbit will win, and whether it is a prize worth chasing.
- jojobas 3y agoThe stated goal of federated everything is not too shabby.
- davidgerard 3y agoit's extremely easy to state very cool goals, and even better when you present some impenetrable code that barely works to go along with them
- pfych 3y agoGlad to see a bit of conversation here about Urbit and competitors. I had a brief go at Urbit, running it on my server and interacting with the community. While it was an interesting take on networking and when it worked it worked great, when it didn't work, it was a fucking nightmare to fix, my planet is still stuck after an update and I inevitably gave up. I'm glad to see Plunder having another go at the ideas Urbit had, some of it was really interesting and it'll be cool to see how these ex-devs run with it.
- pyinstallwoes 3y agoI am biased with my own opinion of Urbit, as I’ve been visited by similar muses desiring similar results. Urbit to me today in its path and form resemble an ontological existential crisis resembling sleight of hand resulting in incompatible execution with what the vision was. It probably did not help to have the visionary spirit literally lost due to various reasons one may argue to various character issues. The idea of Urbit is very interesting, the initial older premise was sound. The current execution is a fallacy of its own goals. It does not replace computing. It does not even proxy it. It literally is built on top of everything else which it directly against the impetus of the project in the first place. A total new way to solve computation with no baggage was a great vision; especially one that was a sort of Maxwell’s minimally defined set of functions that represent computing forever and ever in the most reducible form. The ideas still have legs. The project doesn’t. It forked into a territory that is unable to fix itself. It would have to abandon all “jets” and all bs cryptohype nuisance as well. Love the original design.
- pfych 3y agoI ditto a lot of the opinions stated here. The vision of redesigning computing and networking was novel. But as a developer, when I started diving into it and writing code to interact with it, I started to see all the cracks. Its a shame.
- check89 3y ago> especially one that was a sort of Maxwell’s minimally defined set of functions that represent computing forever and ever in the most reducible form. Can you elaborate?
- chubot 3y agoNot OP, and I don't understand Urbit particularly well, but I think this part of the doc is the salient feature: > The data model of Nock is the noun (*), which is either a natural number (@, called an "atom") or a pair of nouns > The noun is famously simple; it competes with the list as the simplest possible recursive datatype All code and all data is like that. So to me it's basically a Lisp-y networked operating system. This also makes it very inefficient, which the doc explains. But the idea is to build everything on top of the most minimal axioms, which never change.
- brabel 3y agoThis just describes Lisp (itself a materialization of the lambda calculus, which is your "Maxwell equations of computing")?!
- pyinstallwoes 3y agoIt specifically refuted lambda calculus as both minimal and rigorous due to the stipulation of code as data vs data as code. Nouns also being more general than lists.
- mhuesch 3y agosort 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 https://git.sr.ht/~plan/plunder/tree/master/item/doc/PLAN.md
- ks2048 3y agoOkay, I tried to read some of this, just like I tried once years ago to look at what is Urbit, and I don't get it. Maybe it's profound, but if you can't write roughly two paragraphs that clearly describe it, I'm out.
- Nursie 3y agoUrbit - Weird ass hierarchical distributed computing framework with aspects of cultishness. Some sort of combined bytecode vm and networked server process, that is only allowed to participate in the network if your access is blessed by someone further up the hierarchy. It is riddled with jargon, has its own languages nock (the bytecode) and hoon (a higher level) which use their own sorts of conventions and their own terms to talk about them. In a sort of scientology-ish kinda way, the jargon appears to be explicitly designed to separate the in-group from others. The whole thing was originated by a man (Curtis Yarvin) with some very questionable political views, and even though he isn't directly involved in the project any more, he seems to have baked some of them into his design of the system. It has been around for about 13 years and is one of those "we're going to change everything!" projects that never really gets off the ground, but has a tranche of true believers. At this point it's probably something to be filed in the same sort of mental folder as TempleOS, though with less religion and more authoritarianism. From a quick read, 'Plunder' appears to be an attempt to use similar ideas to make a slightly more functional system. As such I'd regard it as a little like FreeZone scientology - a splinter group who can see the issue with the church, but still believe in the fundamental model for whatever reason.
- jitl 3y agoAlso you need to buy a thing kinda like a domain name using Etherium? Or something? There was some noise on HN whenever Urbit did cryptocurrency things and had started an ICO or NFT sale of those things at the height of recent cryptocurrency moment. It’s a system that’s explicitly designed to be really hard to understand and use. Why would that get adopted? How will that succeed?
- pram 3y ago
- cvoss 3y agoAre there any HNers around who can offer some good context for this? While reading this, the list of words I'd never heard before as a software engineer grew very long. I started looking some of them up, found a glossary, and that only served to increase the list of unknown words exponentially. Jet gate core Hoon battery. I still don't know what I'm dealing with. It sounds like a really awesome system on the one hand, and sounds like smoke and mirrors on the other. What are Plunder and Urbit, actually?
- pfych 3y agoI loathe Urbit for naming everything how it's named it, to quote this article: > "Do we really have to be bound by what he received from aliens during an acid trip?" Urbit, and plunder, TLDR from someone who dipped their toe into urbit a year or two ago (marking things I'm still uncertain about with "?"): A from scratch system and networking "protocol"(?) that features its own micro-languages. You can write programs which communicate with each-other, and their state is somewhat synced between users(?), meaning it's possibile to pick state back up from elsewhere as a user. However this is all underpinned with a purposefully cryptic language, horrific political stances by developers, and really not developer friendly interfaces for creating programs. Also, since urbit was really the first attempt at this idea, it does not scale very well and suffers from major scalability issues relating to the amount of data being thrown around by users and their apps on the network. Honestly, writing this out I've probably done a shit job at explaining it but this is what I thought about it after using it for 6-7 months as a hobbyist. I dont use it anymore, but I'm still quite interested in the idea of a "from scratch" micro language that can run on anything. The idea of Perma-computing[^1] I guess? [^1]: https://permacomputing.net/ https://permacomputing.net/
- Moon_99 3y agoUrbit is ok, give it a minute.
- thrtythreeforty 3y agoI am not an Urbit enthusiast but I did spend some time back in 2015 trying to grok their docs. So I was able to read this doc successfully. (It is exceptionally well written for such an obscure topic, one which is often intentionally obfuscated.) Urbit terminology is obscure, probably intentionally so. (As an example, Urbit picked 0 = true and 1 = false, just because it's different than what you're used to.) Nock is a virtual machine that defines only a few primitives. If I recall correctly, there is no "add," only +1. If you want to add 2, run +1 twice. The intent is that the VM is so impossibly simple that there is nothing to add. Just express whatever new semantics you want in terms of the frozen core. A "jet" is a JIT-compiled version of a Nock expression, via pattern matching. The expectation is that the Nock interpreter will notice common patterns and execute some identical, but faster, computation under the hood to evaluate a jet. To continue the example, repeated application of "increment" could be lowered to the machine's add instruction. (However, I was under the impression that the pattern matching happened automatically, but it apparently involves Nock primitive 11, which is... less elegant. Sounds like Plunder gets this part right.) Hoon is a small language on top of Nock ("typed Nock" if you like, but I understand that also macro-expands to pure Nock). I find it absolutely impossible to read because it makes extensive use of sigils ("runes"). A gate is a Hoon function. An arm is basically a member method or namespace member function. You get the idea. The article does a good job of using the more-standard term to describe the remaining pieces: arvo (kernel), vane (driver), etc. Since Urbit is so opinionated on these, my prediction is that eventually someone is going to steal one or two Urbit terms to describe something another system does - probably "jet" if I had to guess - and that will be Urbit's ultimate legacy.
- monero-xmr 3y agoI really don’t see what the big deal is with Urbit / Curtis Yarvin. Sure he wants a monarchy - there are other extremists who want communism. At least monarchies exist today and are quite successful (Saudi Arabia) while no communist countries have resulted in anything worth repeating. https://unherd.com/thepost/curtis-yarvin/ https://unherd.com/thepost/curtis-yarvin/ It’s an interesting thought experiment but I agree with Churchill on democracy being a bad form of government, yet better than all alternatives I can think of.
- woah 3y agoPicture, if you will, a Porcupine Orchestra System, architected on a foundation of Jellyfish Gargoyles and Bamboo Fairies. In this system, the user interacts with the Crocodile Concierge, a unique interface layer that acts as a portal to the Foggy Marshlands, the computational region of the application.
- dboreham 3y ago’Twas brillig, and the slithy toves Did gyre and gimble in the wabe
- hn_urbit_thr123 3y agoIt's disappointing how much low-effort bashing there is in this whole thread. Sure urbit is weird and has a lot of baggage and questionable design decisions, but the project we're discussing is explicitly an attempt to separate out a few good ideas and remove the bad parts. Is that really deserving of casual mockery? I know I'm shouting into the void here, and under a pseudonym to boot, but this is an active FOSS project that real live people work on in their spare time because they hope it'll be important and useful. I like to think it's a convention here not to shit on such people for comedy value.
- xixixao 3y agoParent is perhaps comedic but has a valuable point: This writeup is unapproachable for a general audience due to heavy use of meaningless (“brand”) names. For me it’s also a red flag: Neither system seems to be designed to be approachable. One or two brand names are OK, but these systems seem to use them way too liberally.
- hn_urbit_thr123 3y agoIf you decided to make a fork of linux, and wrote an article explaining why, would you expect it to be easily comprehensible to someone who's never used linux?
- 3y ago
- lazzlazzlazz 3y agoInteresting, but absolutely tragic that the authors of Plunder have decided to stick with the obscurantist, deliberately opaque and illegible manner of talking about their system. I love the intention and think many readers here on HN are unlikely to appropriately value Urbit (and decentralization broadly), but it seems some of Urbit's lessons were not learned.
- Nursie 3y agoI find it impossible to know if there is anything of value in there. On the surface it looks like a set of weird ideas clothed in intentionally (as you say) obscurant terminology. As for decentralisation, can a system that appears to be so explicitly bound in hierarchy actually be said to be decentralised? Certainly it seems to be a distributed system, but AFAICT the actual power in the system is entirely centralised, though delegated through various layers. Maybe I'm just not reading it right, which would be their intention I guess...
- ok_dad 3y agoIt’s not that opaque or obscurantist, the words aren’t hard to understand. I only read this once, and didn’t really look up anything than what a “jet” is, but here it goes: Plunder is a definition of what they want to become a foundational system of computation that will allow past, current, and future systems to run any program. This is achieved by three parts: Plan is the computational model. It defines four things, pins (basically, global singletons), laws (defined functions), apps (partially applied functions), and nats (natural numbers). There are 5 axiomatic operations defined as well. Sire is a language used to bootstrap the plunder system. I don’t get how that works yet but it seems like an implementation detail we don’t need to know unless we’re developing a new plunder virtual machine runtime. Cogs are processes running in the virtual machine runtime that interface with calls to system hardware. They’re the programs you’re running on your virtual machine, like a message (email) client. I don’t get how this works yet, but again that seems like a detail for plunder cog programmers. The rest of the strange words are generally urbit terms that aren’t a part of plunder. Arvo seems like the urbit operating system, nock is its bytecode like plan, hoon is a language that compiles to nock, and terms like noun or subject are just terms within the urbit model like pin or law. None of this stuff is alien language. I think the concept here is that the program is the data is the state is the program. If you look at the state of a plunder system it’ll effectively be a big serialized string of the plan language. The power here is supposedly that no authority can override your desires on your plunder system because it will eventually be a frozen spec, and so virtual machine runtime implementations that are correct must run any program from any time after the freeze. That means a vm I make today will run programs a thousand years from now (probably inefficiently) and a vm created in a thousand years must run programs from today. Theoretically speaking.
- 7373737373 3y agoZot [0] may also be an interesting "pure" base - every natural number is a valid program [0] https://web.archive.org/web/20160102004721/http://semarch.linguistics.fas.nyu.edu/barker/Iota/zot.html https://web.archive.org/web/20160102004721/http://semarch.li...
- eterps 3y agoThe objective outlined at https://git.sr.ht/~plan/plunder https://git.sr.ht/~plan/plunder is certainly compelling: Plunder is a new programming model where programs run forever. Hardware restarts are invisible to the software, as is moving a running program from one physical machine to another. Because of this, programs don't need to save their state into an external database, they can simply keep everything "in memory", and that state will be synchronized to disk transparently.
- sol_plunder 3y agoThe paradigm is quite difficult to describe well. Another attempt is here: https://git.sr.ht/~plan/plunder/tree/master/item/doc/PLAN.md https://git.sr.ht/~plan/plunder/tree/master/item/doc/PLAN.md
- lemper 3y agohow similar is plunder to erlang's vm? a program can run without the need to know the hardware. iirc, mr. armstrong (r.i.p.) once told a story about a running program that was moved across the ocean.
- sol_plunder 3y agoThere 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.
- davidgerard 3y agoso Urbit seems to be an incompetent plagiarism of Nix: https://awful.systems/comment/279#person-listing https://awful.systems/comment/279#person-listing https://awful.systems/comment/287#person-listing https://awful.systems/comment/287#person-listing note how Yarvin claimed he was working on Urbit since 2002, but didn't drop any code until 2010. EDIT: the Lemmy links above are hard to read. Here's a clearer cut'n'paste of the text and the claims: https://reddragdiva.tumblr.com/post/724590682207141888/so-it-turns-out-urbit-is-a-bad-crib-from-nix https://reddragdiva.tumblr.com/post/724590682207141888/so-it...
- Nursie 3y ago> working on Urbit since 2002, but didn't drop any code until 2010. And here we are in 2023 and wikipedia says that as of last year the main thing it can do is ... a bare bones text-based message board. 20 years well spent!
- davidgerard 3y agoin fairness, I recently rewrote the Wikipedia Urbit article myself, to fix the sourcing :-)
- Nursie 3y agoHa! Hilarious. Now do bitcoin ;) TBH after looking into plunder a little more, this whole area starts to feel a bit like "Nano" and their excursion into trinary computation. What are you trying to do? Deliver a rapid P2P application development environment with built in auth. How are you going about it? By redefining computation from the ground up, discarding standard memory models, reorganizing the whole internet into a hierarchical... Yeah, let me stop you there. Maybe do one thing at a time and demonstrate how great it is before moving on with this magnum opus.
- sol_plunder 3y agoMain 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. 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.
- Nursie 3y agoI read your intro to PLAN. It's much easier to understand than anything I've read on this sort of topic before. I can at least come out of it understanding what the aims are and what it might provide. 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.
- sol_plunder 3y agoThe 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 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.