Pauan

By the way, you can use the above `Component` system immediately with dominator, you don't need to wait for me to add anything. I've tried hard to make dominator flexible...

> Such a component cannot have it own state. But with the help of futures-signals, it's possible for an app to put everything (data) in a single app-state with very...

> As I understand, the Msgs would be sent from the current Component to itself. Yes, that's correct. I mentioned earlier in this thread that that is a big limitation...

> But, the readme isn't giving me much. Sorry about that, improving the docs is definitely high up on my TODO list. > What kind of FRP? Do you have...

> How does this compare to Carboxyl? I had taken a look at all of the Rust FRP libraries before making my own. All of them (including carboxyl) follow the...

> Yes, but for what? Based on what you said it seems like you mean you were looking for one language which you could use for basically everything. So a...

I've improved the TodoMVC example so that it's properly modularized into separate files: https://github.com/Pauan/rust-dominator/tree/master/examples/todomvc/src

> If I understand correctly it uses keyed reconciliation of lists just like a VDOM. As I understand, that's fast. Yes, but it's *not* fast, it's actually worse than `O(n)`...

> @limira have you ever encountered this problem? If yes, how do you solve it? That's a good question. I do indeed have some duplication between the client and server:...

> In every app I've seen, the keyed list parts are isolated pieces of the app. "Isolating" it doesn't change the `O(n)` cost. And as soon as a parent component...