on master help sign in
Update the-100-year-computer.md

I made some minor changes. But I am worried that this is too terse to convey what we actually mean. "Imagine a computer that was extremely valuable to you, that you’d pay thousands of dollars to recover, but you used *less* than the one you do today. " This is confusing as hell. Are we saying that you would need to pay thousands of dollars to recover it? That that might happen? Why do you use it less than you use it today? Because it's just a better machine that needs less use? Are we saying that it's so valuable that you'd pay so much even for a device you rarely use? So, general thought: we are trusting the reader to pick up on our hint too much.

commite46d34dd8790986e5cc0217b0fd91e96a67780c7 authorrmariani <robert@tlon.io> dateMon 13 May 2019, 17:28 (7 years ago) parent07585a5
1 file changed+5−5
content/posts/the-100-year-computer.md+5−5
content/posts/the-100-year-computer.md+5−5
@@ -1,8 +1,8 @@
11+++
2−title = "The 100 Year Computer"
2+title = "The 100-Year Computer"
33date = 2019-05-13
44author = "Galen Wolfe-Pauly"
5−description = "One way to think about Urbit: as a \"100 year computer.\""
5+description = "One way to think about Urbit: as a \"100-year computer.\""
66[taxonomies]
77posts = ["Essays"]
88+++
@@ -11,9 +11,9 @@ posts = ["Essays"]
1111
1212Around the Tlon office, we’re always looking for more concise ways to describe what we do. We kicked around ‘personal server’ for a long time. It’s pretty close. ‘Personal cloud computer’ did okay for a while, but it’s a little confusing.
1313
14−One way to think about Urbit is as a 100 year computer.
14+But another way to think about Urbit is as a 100-year computer.
1515
16−A 100 year computer has to be durable, reliable and permanent. It has to never lose data or fail in unpredictable ways. It has to be continuous, meaning it should never need to be updated by the user. If I put it in a closet for 10 years and take it out, it should work again without any intervention.
16+A 100-year computer has to be durable, reliable and permanent. It has to never lose data or fail in unpredictable ways. It has to be continuous, meaning it should never need to be updated by the user. If I put it in a closet for 10 years and take it out, it should work again without any intervention.
1717
1818And, perhaps most importantly, it should be easy and enjoyable to use. Both for a casual user and for a technical person. If it’s not enjoyable to use, and doesn’t actually *get used*, it’s never going to survive for 100 years.
1919
@@ -23,4 +23,4 @@ Imagine that a computer was something you kept forever. It would comfortably sto
2323
2424Imagine a computer that was extremely valuable to you, that you’d pay thousands of dollars to recover, but you used *less* than the one you do today.
2525
26−**Galen Wolfe-Pauly** ~ravmel-ropdyl
26+**Galen Wolfe-Pauly** ~ravmel-ropdyl