Realization: The fact that the DOM and UI libraries are always single threaded and the fact that Rust has a difficult time expressing DOM/UI memory management patterns are actually pretty much manifestations of the same problem.
-
-
Replying to @pcwalton
is it the state management with message passing (of events) in a tree which actually ends up with a quite connected graph of possible interactions? I've been thinking about this for years and the only things I can come up with are encapsulating and exploiting static structure.
1 reply 0 retweets 1 like -
That is, facilitating local interactions (by flattening the ownership) while using something else (more akin to IPC RPC) to glue these local subgraphs together, and then heavily specialize & optimize the resulting mess away. I haven't gotten as far as testing any of this, sadly.
1 reply 0 retweets 0 likes -
Replying to @eddyb_r
At this point I'm inclined to just have a per-Window Slab of Views and refer to all views by index. All View methods are methods on (Window, index) pairs.
2 replies 0 retweets 2 likes
Rationale: It's like a global per-Window lock, which is how all existing UI libraries work anyhow.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.