Funny you should mention Clojure -- a language that I found to not bestow any appreciable performance, abstraction, or usability advantage compared to a halfway decent Scheme-on-Java such as Kawa, yet still be different enough to be annoying.<p>If you like Clojure, don&#x27;t let me stop you. But I&#x27;ve shipped servlets written in Scheme that did millions of dollars in business... forgive me if I personally am a bit slow to accept that Rich Hickey has brought us fire from the gods.<p><i>In other words, even if your claim is true, it describes almost every project in computing in the last 15 years.</i><p>Now you see why when tickets go on sale for the next language, framework, or OS hypetrain, I&#x27;m quite reluctant to buy.<p><i>That said, the old &quot;it&#x27;s just typical Moldbug&quot; trope isn&#x27;t much better than the propaganda his followers spout, and the rest is pretty weak too.</i><p>Urbit is almost never presented as &quot;here&#x27;s an interesting pure-functional VM and OS abstraction layer I&#x27;ve been working on, I think its advantages are this-and-such&quot; but Grand Pronouncements like &quot;The Internet Has Failed. We are writing its successor. Join us. It is your destiny.&quot; The rationale is that since data silos are more common and accessible than distributed systems and ISPs are dickheads on the modern internet the internet itself is architecturally unsound. But data silos and dickhead ISPs are much more a social problem than a technical one, and I never heard <i>technical</i> reasoning for why the internet is broken from the Urbit folks.<p>It&#x27;s always &quot;Google, Facebook, AOL, Comcast, therefore Unix and the internet are broken.&quot; But there&#x27;s no chain of reasoning in the middle. It&#x27;s a rhetorical cup-and-ball game.<p>And when I challenge the Urbit folks on this and tell them that I see no benefit to Urbit that I can&#x27;t get from other more battle-tested systems, and that Urbit is different enough to be annoying without being advantageous, I get one of a few stock responses:<p>&quot;That was fine for 1975. We&#x27;re trying to build a system for 2015.&quot;<p>It is 2015 (now 2016). You still haven&#x27;t specified in any detail how the system I run every day isn&#x27;t up to the task.<p>&quot;We want to make administering your server as easy as administering your smartphone.&quot;<p>Smartphones are administered largely from afar, by actors whose interests mainly do not coincide with my own. So I don&#x27;t think that&#x27;s a goal you can really reach without severely compromising your vision.<p>&quot;In practice, Hoon is really easy and pleasant to use.&quot;<p>So is Scheme. So is Haskell if you want to go full functional. So is C once you adopt certain simple practices. How, exactly, is Hoon easier and more pleasant than these?<p>&quot;Uhhh, yeah, we&#x27;re working on making the documentation clearer and the names less weird...&quot;<p>Good. I might check again when that work is completed.<p>I&#x27;ve encountered arguments of this type (Grand Pronouncements of the doom of the status quo, stock phrases as to why our system&#x2F;product is better with a dearth of reasoning) before. It never, ever comes from a good place.<p>And I totally get the desire to play at being Alan Kay. But doing that successfully requires Alan Kay levels of insight into how computers and brains work deep down, which Moldbug hasn&#x27;t convinced me he has.