rust-memory-container-cs VS yew

To fix the problem, smart pointer is the go-to, in this case at least. Someone made a cheat sheet for memory containers, and I thought might be useful to share it here.

With Rc, it was failing as I'm using rayon for multi-threaded rendering and Rc is not Sync (that's what I understand from: the Rust memory container cheat-sheet

I agree with you here, but it's disingenuous to claim that the Cell family are not an intentional and necessary part of the design of Rust's ownership system; I would be interested to see any sort of documentation or RFC commentary that implies otherwise. Even a simple 'Rust 101'-style cheatsheet makes it apparent that they're very much a small but necessary part of the whole: https://github.com/usagi/rust-memory-container-cs

Yew is a framework for creating reliable and efficient web applications. Yew

I coded up a game of life implementation in rust and web assembly using https://yew.rs/ as an effort to sharpen my rust skills and it resulted as a fun toy. You can find the source here: https://gitlab.com/reedrichards/wvdom Enjoy!

UI template: Yew - (https://yew.rs/)

I'm surprised nobody said they'd use [Yew](https://yew.rs/), especially given the premise of this being for a passion project.

This example shows updating an existing state: https://github.com/yewstack/yew/blob/04909dd942eb64285652d96a2621bdf7be3fa912/examples/timer_functional/src/main.rs

1. Not related to npm, but related to the web.

2. True, but compilers are generally better than transpilers.

3. Have you seen https://yew.rs/ ?

You could use Yew to write web apps, which can be opened on Android phones.