I 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

I 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/