ux-charts VS yew-components

ux-charts for the lazy

This post is about Clutter-rs. We have just moved from being "actively developed" to being "as is" for Clutter-rs and Cogl-rs. Documentation about Angular Rust on https://angular-rust.github.io/ is underway. Some documentation is ready, all that remains is to make editorial changes. If you need developer documentation about Angular Rust, check out https://docs.rs/ux-framework. Some nice samples are ready here https://github.com/angular-rust/ux-samples

UX Charts is a drawing library designed for clean charts. UX Charts supports various types of backend including GTK/Cairo and HTML5 Canvas. UX Charts are designed with the concept - "one code for all". It uses the UX Dataflow library as the data source and the UX Animate library as the canvas implementation.

What am I saying? That Rust will end the era of JS in the browser? I don't know - probably not. JS can be really fun too. But there already is an Angular Rust project, WASM integration into some desktop application frameworks, and several rapidly growing WASM projects, so things are moving in an interesting direction. At my current work we were able to compile an entire backend rust service into a WASM module that gets loaded into a Vue based UI. We then stream the context that the backend service is receiving to the WASM module and we can "see" the output the service will be producing, in (throttled) realtime - but it's available in the browser with zero load on the backend service itself needing to deliver that data. It's a very interesting application of Rust and provokes thoughts of new alternative architectures.

Web sample made on top of Yew using ymc - Material Design Components for the Yew framework