Surprisingly, ‘completely’ is not even an exaggeration — the front-end, too, is written in Rust, using the Yew library (lobste.rs thread), which compiles to wasm to run in the browser and render the DOM . Nice!
I also like the fact that Yew is Elm+React-inspired. The Elm architecture is fantastic to work with. Neat detail, though: where Elm attacks shared mutable state by making the state objects shared but immutable (state + events -> new state), in Yew the state is mutable but unshared (Rust prevents writing code that would cause simultaneous updates.)
All of the above written without having used Yew myself, only some Elm and hardly any Rust, so please add grains of salt as required.
That was also my number one takeaway from the article. I knew about compiling to WASM targets but had no idea the front end story included full frameworks like Yew.
Surprisingly, ‘completely’ is not even an exaggeration — the front-end, too, is written in Rust, using the Yew library (lobste.rs thread), which compiles to wasm to run in the browser and render the DOM . Nice!
I also like the fact that Yew is Elm+React-inspired. The Elm architecture is fantastic to work with. Neat detail, though: where Elm attacks shared mutable state by making the state objects shared but immutable (state + events -> new state), in Yew the state is mutable but unshared (Rust prevents writing code that would cause simultaneous updates.)
All of the above written without having used Yew myself, only some Elm and hardly any Rust, so please add grains of salt as required.
That was also my number one takeaway from the article. I knew about compiling to WASM targets but had no idea the front end story included full frameworks like Yew.