[weare138]

>Summarization: Urbit is a reaction to Unix-driven software complexity that dominates modern software development.

I keep reading explanations about Urbit along these lines but what's perplexing about this explanation is Urbit does nothing to achieve this goal. Regardless of the fact that Urbit is referred to as an operation system it still isn't one. It relies on a conventional OS, often UNIX family OS's like Linux to run. Urbit just layers a new even more complicated software and networking stack on top of the 'Unix-driven software complexity' that still underpins Urbit. Urbit does nothing to address these problems, it just makes them worse. Urbit's underlying software stack (Nock, Hoon, etc.) is just bizarre and non-nonsensical. For example, this gem from the docs:

"A loobean is a Nock boolean - Nock, for mysterious reasons, uses 0 as true (always say "yes") and 1 as false (always say "no")."

Wat? Why?!? And it doesn't end there. Urbit is littered with these WTF design choices and terminology. No one in their right mind is going to build professional software solutions on a platform like this. You might as well just be developing software in something like Brainfuck.