@@ -1,11 +1,13 @@
4title: Common objections to Urbit
4title: Common objections to Urbit
5author: Curtis Yarvin
5author: Curtis Yarvin
6−preview: Some common objections to Urbit, refuted.
6+preview: Some common objections to Urbit, discussed.
7+image: http://media.urbit.org/site/blog-9.jpg
7layout: urbit,post
8layout: urbit,post
8footer: true
9footer: true
9navmode: navbar
11navmode: navbar
10navdpad: false
12navdpad: false
11navselect: posts
13navselect: posts
@@ -38,7 +40,7 @@ Here's our list right now:
38*"We choose to go to the moon, not because it is easy, but because it is hard."*
40*"We choose to go to the moon, not because it is easy, but because it is hard."*
39— John F. Kennedy
41— John F. Kennedy
41−<h2 id="prime">Urbit is not ready for prime time.</h2>
43+<h2 id="prime">Urbit is not ready for prime time.</h2>
43**TLDR**: we agree.
45**TLDR**: we agree.
@@ -104,7 +106,7 @@ Two implementations are incompatible, but each swears it has the
104right interpretation of the natural-language spec. This simply
106right interpretation of the natural-language spec. This simply
105cannot happen in the Nock world. If two implementations
107cannot happen in the Nock world. If two implementations
106disagree, at least one of them is incorrect. This puts us firmly
108disagree, at least one of them is incorrect. This puts us firmly
107−in "with enough eyeballs, all bugs are shallow" territory.
109+in "with enough eyeballs, all bugs are shallow" territory.
109The fact remains, however, that a Nock interpreter without jets
111The fact remains, however, that a Nock interpreter without jets
110is completely useless. And there is not even an informal
112is completely useless. And there is not even an informal
@@ -125,7 +127,7 @@ against the efficient implementation?
126Compared to intrinsics, jets give you true separation between
128Compared to intrinsics, jets give you true separation between
127mechanism and policy; only the interpreter, not the programmer
129mechanism and policy; only the interpreter, not the programmer
128−and not the compiler, needs to know what's accelerated.
130+and not the compiler, needs to know what's accelerated.
130Compared to an FFI, jets preclude I/O, so can be trivially
132Compared to an FFI, jets preclude I/O, so can be trivially
131sandboxed. Except that the programmer needs to mark routines
133sandboxed. Except that the programmer needs to mark routines
@@ -159,7 +161,7 @@ state and the current event.
159Urbit defines the semantics of a complete event log. It doesn't
161Urbit defines the semantics of a complete event log. It doesn't
160and can't require an implementation to maintain the whole log.
162and can't require an implementation to maintain the whole log.
161It can maintain a checkpoint and the log since that checkpoint.
163It can maintain a checkpoint and the log since that checkpoint.
162−The current implementation of Urbit maintains
164+The current implementation of Urbit maintains
164However, any practical urbit maintains a periodically updated
166However, any practical urbit maintains a periodically updated
165checkpoint. Our present implementation doesn't provide a way to
167checkpoint. Our present implementation doesn't provide a way to
@@ -658,7 +660,7 @@ integration, also integrated with a reactive web server, are
660<h2 id="dictator">Urbit is a reactionary digital
662<h2 id="dictator">Urbit is a reactionary digital
661−dictatorship.</h2>
663+dictatorship.</h2>
663**TLDR**: Facebook is a digital dictatorship.
665**TLDR**: Facebook is a digital dictatorship.
664Urbit is a decentralized network with a republican constitution.
666Urbit is a decentralized network with a republican constitution.