git.iko.soy/urbit.org
on master help sign in
fora links
2fe1c77Galen Wolfe-Pauly
main/blog/2017.5-frozen.md+2
compare with master
unifiedsplit
@@ -126,3 +126,5 @@ Perhaps the best example of the convergent style in existing, mature system soft
126The lesson: when we see a system that seems to want to expand indefinitely, we can and should look for a layer division within this system, separating an inner layer that tends to converge from an outer layer that naturally diverges. Layering is what distinguishes true system software from the giant balls of mud that all deep codebases want to become.
126The lesson: when we see a system that seems to want to expand indefinitely, we can and should look for a layer division within this system, separating an inner layer that tends to converge from an outer layer that naturally diverges. Layering is what distinguishes true system software from the giant balls of mud that all deep codebases want to become.
127
127
128Are all balls of mud, or at least all the muddy parts of an OS, susceptible to this transformation? We think so. But we'll see.
128Are all balls of mud, or at least all the muddy parts of an OS, susceptible to this transformation? We think so. But we'll see.
129+
130+As usual, comments are on fora. Check out [this thread](https://urbit.org/fora/posts/~2017.5.12..20.30.11..0050~/).
main/blog/2017.5-plans.md+3−1
@@ -67,7 +67,7 @@ Note that we remain a super-tiny team. We’ve had some serious outside contrib
67
67
68After `cc-release` this summer, we’ll move from bottom-up, infrastructure-driven engineering, to top-down, user-driven engineering. Naturally this is `dd-release` (deck-directed).
68After `cc-release` this summer, we’ll move from bottom-up, infrastructure-driven engineering, to top-down, user-driven engineering. Naturally this is `dd-release` (deck-directed).
69
69
70−Our planning target is a stable, useful Urbit we can ship in 2017, with roughly our present resources. Since we’re working top-down, we can abandon the deep architectural essays and work, like normal human beings, from an illegible list of features scribbled on a poorly-erased whiteboard.
70+Our planning target is a stable, useful Urbit we can ship in 2017. Since we’re working top-down, we can abandon the deep architectural essays and work, like normal human beings, from an illegible list of features scribbled on a poorly-erased whiteboard.
71
71
72## A whiteboard list
72## A whiteboard list
73
73
@@ -120,3 +120,5 @@ If you know the current maintenance Urbit, you know that most of these features
120Also, since this is the release after the release we're doing now, we're probably missing as many checkboxes as we've caught. And triage is a thing that happens. It's really better understood as the *kind* of work we're going to do.
120Also, since this is the release after the release we're doing now, we're probably missing as many checkboxes as we've caught. And triage is a thing that happens. It's really better understood as the *kind* of work we're going to do.
121
121
122We'd really like to get all these things done in 2017. But a lot depends on what kinds of resources we have access to. And of course, as we document the system, it gets easier for all the people who believe in Urbit to help us build it.
122We'd really like to get all these things done in 2017. But a lot depends on what kinds of resources we have access to. And of course, as we document the system, it gets easier for all the people who believe in Urbit to help us build it.
123+
124+As usual, comments are on fora. Check out [this thread](https://urbit.org/fora/posts/~2017.5.12..20.33.04..3db0~/).