I've always heard: do one thing and do it right. It's the Unix philosophy, before it was totally disregarded. Urbit seems to take the total counterpoint of thi

I've always heard: do one thing and do it right. It's the Unix philosophy, before it was totally disregarded. Urbit seems to take the total counterpoint of this advice, and I wonder whether it's a good idea. What I don't get is what it is trying to achieve. The stated goal are too abstract. What are some use-cases? Is it really necessary to scrap the whole OS and languages to achieve these goals? I do sympathize with the idea of rewriting everything from scratch, and I too feel that "almost everything is terrible" in software-land. But I doubt rewriting everything without having a firm grasp on the underlying issues is the way to go. It it a fun exercise, and inspiring besides, but I'm unsure it can be more than that.