limira

Maybe my poor words cause misunderstand here? The code I link to `dominator` is also in an event handler and not mutate the state during rendering too. What I refer...

To make it clear, this proposal is not about *forbidding* state change in the renderer. But just the ability move the mutating codes out of the renderer and the renderer...

I'm not experienced enough to say *exactly how* I want it to be, especially for a crate that I never use before. If you are happy with how it is...

I just do [an experiment here](https://gitlab.com/limira-rs/mico). It may be one of the ways to solve this. Admittedly, I am not sure if there is any problem with my approach because...

> I don't think it requires a new framework That's why I do not release it on crates.io yet. And do not bother to register a placeholder for `mico`.

> pub trait Component > Unfortunately it doesn't solve the "push messages to higher components" problem, this is only for self-contained components. In Mico, the `trait Component` above is actually...

> The purpose of components isn't for performance (in Elm, creating components does not increase performance). I only have very limited experience with React (few weeks), and some with Yew...

> For TodoMVC (removed comments), > Svelte: 149 lines, 1913 characters without white space. > Rust-Dominator: 429 lines, 6880 characters without white space. > That's quite an extreme difference Adding...

> > Another difference is that both Dominator and Elm have static typing. That adds some extra lines because you have to define your types (e.g. the Filter, Todo, and...

> My feel is that FRP is verbose I work with it about 2 months now. I actually feel that it is verbose too. The verbosity in the view render...