I guess you're familiar with Richard Gabriel's Worse is Better, with the idea that projects that get 80 % there fast with gaping conceptual holes in them outcompete projects that go for the 100 % and get bogged down trying to get the difficult bits just right. We seem to still be very much in a worse is better landscape, and Urbit fits in with the opposite sorts of systems that have been getting their clocks cleaned by quicker and dirtier approaches since the 1980s.
Is there a plan for how Urbit and its tight tolerances approach are going to survive in real world software ecosystems where things often get unpredictably chaotic over both social and technical dimensions?
Chaigidel7 karma
I guess you're familiar with Richard Gabriel's Worse is Better, with the idea that projects that get 80 % there fast with gaping conceptual holes in them outcompete projects that go for the 100 % and get bogged down trying to get the difficult bits just right. We seem to still be very much in a worse is better landscape, and Urbit fits in with the opposite sorts of systems that have been getting their clocks cleaned by quicker and dirtier approaches since the 1980s.
Is there a plan for how Urbit and its tight tolerances approach are going to survive in real world software ecosystems where things often get unpredictably chaotic over both social and technical dimensions?
View HistoryShare Link