0
Urbit 2.0 just dropped (archive.ph)
submitted 3 years ago* (last edited 3 years ago) by to c/techtakes@awful.systems
7 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
[–] 1 point 3 years ago (1 child)

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.

Yes that's what a spec means. Like wow I can write puts("Hello, world!") and it does the same thing on every ANSI C compiler, how novel!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 3 years ago

    this is an incredibly bad idea for security of course, and is in any case is a garbage version of what javascript VMs already do successfully (much to javascript’s detriment, in some cases)

  • permalink
  • fedilink
  • source
  • parent