submitted 1 year ago* (last edited 1 year ago) by self@awful.systems to c/techtakes@awful.systems

37 comments fedilink hide all child comments

no excerpts yet cause work destroyed me, but this just got posted on the orange site. apparently a couple of urbit devs realized urbit sucks actually. interestingly they correctly call out some of urbit’s worst points (like its incredibly high degree of centralization), but I get the strong feeling that this whole thing is an attempt to launder urbit’s reputation while swapping out the fascists in charge

e: I also have to point out that this is written from the insane perspective that anyone uses urbit for anything at all other than an incredibly inefficient message board and a set of interlocking crypto scams

e2: I didn’t link it initially, but the orange site thread where I found this has heated up significantly since then

you are viewing a single comment's thread
view the rest of the comments

[-] self@awful.systems 4 points 1 year ago

how is the experience of developing for an Urbit-like ecosystem? everything I’ve seen as an outsider indicates it’s fairly painful, but from an esolang perspective I suppose the pain is the point

[-] corbin@awful.systems 6 points 1 year ago

Not just development, but even just basic maintenance of a star is onerous. Worse, there's no guide on how to do it: no notion of security and privacy, no data-integrity recommendations, no backups or testing, and almost no information on key management.

It's so bad that, if you look at Cammy, you won't see any sign of Urbit. You'll just see a language which designates total functions, provably halting, with basic toolchains for compiling and running. No Arvo whatsoever. I did reuse the word "jet", but I've provided an entire theory of jets and holes so that every Cammy jet is implementable in raw Cammy; there's no C code.

Also, although it isn't obvious from the esolang wiki, Cammy is designed to subvert copyright and punish folks who build up private repositories of Cammy code. I figure that if we can have fascist toolchains, then we can also have antifa toolchains.

Sorry for going NSFW, but I figure that my candor in the present will save somebody time and effort in the future.

[-] self@awful.systems 6 points 1 year ago

this is really interesting! thank you for sharing; doing deep dives into urbit can be fairly mentally punishing so I appreciate the first-hand account

it sounds like nobody with experience running any kind of service in prod has had hands on urbit — the administrative bits you mentioned are all the basics you’d want to run a system at any scale, and it’s embarrassing that urbit has none of them after all these years

from what I’ve skimmed so far, Cammy is impressive! notably its wiki article explains everything in standard computer science terms (including explaining things in terms of lambda expressions, which I appreciate) and I get the impression a lot of work went into making it fairly comprehensible for an esolang (as opposed to Urbit, with the opposite goal). I’ll definitely take a closer look at this later tonight, as having a reference “hoon’s non-evil little brother” is definitely useful for understanding Urbit by contrast

there really should be more antifa software licenses in the world. I’ve been exploring options myself to represent similar ideas in the code I release

this post was submitted on 09 Aug 2023

11 points (100.0% liked)

TechTakes

1493 readers

130 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 2 years ago

MODERATORS

dgerard@awful.systems