Very nice talk, I think I'll pick pup a couple tricks from this. Hopefully we'll see some usable implementations of this architecture, as doing even immediate mode ui in Rust is fairly painful at the moment.
This is a very good talk about how to use Rust even better once one is comfortable with the borrow checker and Traits and Associated Types. I think it also helps to grasp what is being said if one has first cloned the Xilem repo and run the two examples in it and looked at the very small Rust source file for each one and wondered how it accomplishes what it does.
Actually enjoyed this talk immensely. You spoke extremely clearly and I took notes. I've used the tuple trait in a project before, and I'll definitely be using it more, it's super powerful at avoiding the Vec Box dyn's
In the javascript framework world we are seeing a move towards signals. Like in solidjs, leptos, or a library for signals only like reactively (there is a great blog post on this one explaining the full tree for propagting state to do the least amount of work). Obviously a vdom or tree like UI can be much faster in something like rust that is much more efficient and easier to parallelize than something like javascript. In react the version of rebuild is render (which isn't actually rendering) and runs via the framework. I have always been curious about the signal architecture inside a UI library outside of the DOM. Very interesting talk. I still greatly enjoy functional programming and programming languages like haskell, so I still like the idea of a more functional UI library and am interested to see where this goes. Especially combined with more of a data oriented design as seen in bevy ECS and other ECS's. Thanks! Also I greatly appreciate your work on wgpu!!
Curious if you considered an "enum oriented" design for the views versus trait objects and what were the trade offs if that was a consideration. thx for any thoughts.
The slides for this talk are here: docs.google.com/presentation/d/1P8Su5mZSYkfZ1A9mPAaKag-vtXmVD8nUBD7Ym-pfwJM/edit?usp=sharing
Very nice talk, I think I'll pick pup a couple tricks from this. Hopefully we'll see some usable implementations of this architecture, as doing even immediate mode ui in Rust is fairly painful at the moment.
This is a very good talk about how to use Rust even better once one is comfortable with the borrow checker and Traits and Associated Types. I think it also helps to grasp what is being said if one has first cloned the Xilem repo and run the two examples in it and looked at the very small Rust source file for each one and wondered how it accomplishes what it does.
Actually enjoyed this talk immensely. You spoke extremely clearly and I took notes. I've used the tuple trait in a project before, and I'll definitely be using it more, it's super powerful at avoiding the Vec Box dyn's
In the javascript framework world we are seeing a move towards signals. Like in solidjs, leptos, or a library for signals only like reactively (there is a great blog post on this one explaining the full tree for propagting state to do the least amount of work). Obviously a vdom or tree like UI can be much faster in something like rust that is much more efficient and easier to parallelize than something like javascript. In react the version of rebuild is render (which isn't actually rendering) and runs via the framework. I have always been curious about the signal architecture inside a UI library outside of the DOM. Very interesting talk. I still greatly enjoy functional programming and programming languages like haskell, so I still like the idea of a more functional UI library and am interested to see where this goes. Especially combined with more of a data oriented design as seen in bevy ECS and other ECS's. Thanks! Also I greatly appreciate your work on wgpu!!
Very interesting talk，thanks
Curious if you considered an "enum oriented" design for the views versus trait objects and what were the trade offs if that was a consideration. thx for any thoughts.
How’d that work? Could you give an example?