git.iko.soy/urbit.org
on master help sign in
style
748b681Galen Wolfe-Pauly
main/blog/2017.4-update.md+9−7
compare with master
unifiedsplit
@@ -19,7 +19,7 @@ Here's our April update, covering the last month or so. I've taken people's own
19
19
20It might help to have a broader roadmap. We'll post that next.
20It might help to have a broader roadmap. We'll post that next.
21
21
22−# ~palfun-foslup (Fang)
22+### `~palfun-foslup` (Fang)
23
23
24I've been focusing entirely on `:talk` work.
24I've been focusing entirely on `:talk` work.
25
25
@@ -31,7 +31,7 @@ Along the way, I took note of and corrected some architectural weirdness, with t
31
31
32*This is not as big as a change as it sounds -- all these partitions use the same mechanisms. It's just about policy limitations. Eg: only a guardian can receive inbound messages and subscriptions. In `:talk`, the separation matches the split between mailserver and mailreader in classic Unix email, news server and news reader in NNTP, etc.*
32*This is not as big as a change as it sounds -- all these partitions use the same mechanisms. It's just about policy limitations. Eg: only a guardian can receive inbound messages and subscriptions. In `:talk`, the separation matches the split between mailserver and mailreader in classic Unix email, news server and news reader in NNTP, etc.*
33
33
34−# ~tonlur-sarret (Keaton)
34+### `~tonlur-sarret` (Keaton)
35
35
36I've started a new multi-part tutorial series on building and deploying Urbit web apps. The goal of the series is to highlight Arvo's technical features and the flexibility of Urbit's API/UI model through interactive code examples and full demos that technical readers can extend.
36I've started a new multi-part tutorial series on building and deploying Urbit web apps. The goal of the series is to highlight Arvo's technical features and the flexibility of Urbit's API/UI model through interactive code examples and full demos that technical readers can extend.
37
37
@@ -43,7 +43,7 @@ I've started a new multi-part tutorial series on building and deploying Urbit we
43
43
44*The main change for the programmer is just that in the present `%arvo` and `%ames` (whose total rewrite is now being tested), message transaction handling is shitty from end to end. But you're used to that. Distributed programming with exactly-once transactional messages is such an awesome experience that even when it's broken, it's kind of ok.*
44*The main change for the programmer is just that in the present `%arvo` and `%ames` (whose total rewrite is now being tested), message transaction handling is shitty from end to end. But you're used to that. Distributed programming with exactly-once transactional messages is such an awesome experience that even when it's broken, it's kind of ok.*
45
45
46−# ~ramtev-wisbyt (Raymond)
46+### `~ramtev-wisbyt` (Raymond)
47
47
48Before 0.5, Urbit ran as a single monolithic process controlling everything from terminal I/O to computing and storing events. In 0.5, Urbit is split into a more traditional database-server architecture. Thanks to a wrapper application, casual users don't have to notice much difference if they don't want to - except that the bottleneck in the old event code is gone, so things are a lot faster. But the new architecture has a lot more flexibility.
48Before 0.5, Urbit ran as a single monolithic process controlling everything from terminal I/O to computing and storing events. In 0.5, Urbit is split into a more traditional database-server architecture. Thanks to a wrapper application, casual users don't have to notice much difference if they don't want to - except that the bottleneck in the old event code is gone, so things are a lot faster. But the new architecture has a lot more flexibility.
49
49
@@ -53,7 +53,7 @@ At the top level, there is a single urbit daemon process which runs in the backg
53
53
54*The new Urbit looks much more like a regular production server. Everything outside the noun library has been replaced. We're also hoping to add FUSE access to the Urbit namespace, though the priority isn't immediate.*
54*The new Urbit looks much more like a regular production server. Everything outside the noun library has been replaced. We're also hoping to add FUSE access to the Urbit namespace, though the priority isn't immediate.*
55
55
56−# ~pittyp-pittyp (Anton)
56+### `~pittyp-pittyp` (Anton)
57
57
58I am in the middle of making an architecture change to the console protocol, with the eventual goal of being able to reconnect sessions.
58I am in the middle of making an architecture change to the console protocol, with the eventual goal of being able to reconnect sessions.
59
59
@@ -65,11 +65,11 @@ I am in the middle of making an architecture change to the console protocol, wit
65
65
66*If you remember the last update, we are obviously asking our console for a lot of UI power. We are also redesigning `:talk` to use it even on the Web. But we have to fix the protocol first.*
66*If you remember the last update, we are obviously asking our console for a lot of UI power. We are also redesigning `:talk` to use it even on the Web. But we have to fix the protocol first.*
67
67
68−# ~ravmel-ropdyl (Galen)
68+### `~ravmel-ropdyl` (Galen)
69
69
70I’m putting together new materials for the public.
70I’m putting together new materials for the public.
71
71
72−# ~sorreg-namtyv (Curtis)
72+### `~sorreg-namtyv` (Curtis)
73
73
74I've done two main things: adding formal decorations to Hoon, and making the Arvo boot sequence coherent.
74I've done two main things: adding formal decorations to Hoon, and making the Arvo boot sequence coherent.
75
75
@@ -79,4 +79,6 @@ For formal decorations, see the accompanying forum post. Briefly, I started fro
79
79
80The parser and AST changes required for decorations also helped me find a way to disambiguate direct and indirect Hoon syntax, eliminating the duplicate irregular syntax introduced in Hoon 151 -- if we want. Backward compatibility was almost perfect, requiring only a few touchups across the whole codebase.
80The parser and AST changes required for decorations also helped me find a way to disambiguate direct and indirect Hoon syntax, eliminating the duplicate irregular syntax introduced in Hoon 151 -- if we want. Backward compatibility was almost perfect, requiring only a few touchups across the whole codebase.
81
81
82+### Oh, and
83+
82−This actually went up on `/fora` before anything else. Feel free to chime in on [this thread](http://urbit.org/fora/posts/~2017.3.1..22.06.50..bf2a~/) with comments and questions.
84+This actually went up on `/fora` before anything else. Feel free to chime in on [this thread](http://urbit.org/fora/posts/~2017.3.1..22.06.50..bf2a~/) with comments and questions. We're here to answer them!