cargo-ui VS flutter_rust_bridge

This time with a couple of new features for [cargo-ui](https://github.com/sixtyfpsui/cargo-ui): It now comes with feature selection and an overview of installed tool chains.

For example, the binary for cargo-ui (https://github.com/sixtyfpsui/cargo-ui) is 7M on my linux system. But we haven't done much size optimization yet, and there probably are lots of low hanging fruits possible with playing with cargo features.

Use some sort of executable file, like webassembly. I've seen extism which is really cool. Though theres no dart port for it or a dart package, i think something could be done via flutter_rust_brige. This will allow people to use the languages supported via extism (js, go, rust, zig, cpp etc) to their full potential and have the language's ecosystem available and they can just compile the plugin to a wasm file and use it in the app. Downsides would be ig using that rust package in dart since flutter_rust_bridge does have some amount of complexity. And that for example, two plugins both written in say for example js, depend on some sort of http package, and both plugins load the same package twice in their respective wasm files. ig plugin files would be more larger in the end.

Not a Flutter Dev, but have you tried 'flutter_rust_bridge' [0]. Seems provide some interop between flutter and rust and looks like a popular and active project. I'm native mobile dev and just curious about this kind of interop myself. If it's seamless then looks like good balance to do mobile front-end in flutter and mobile backend in rust.

[0] https://github.com/fzyzcjy/flutter_rust_bridge

This template is primarily built using the flutter_rust_bridge library. It also incorporates several popular packages and modifications into the default Flutter template, ensuring optimal development process. It has been designed with future scalability and performance in mind.

If you want example code, the flutter_rust_bridge uses a webworker pool with shared memory on the web to multithread the execution.

There's also the thing that flutter_rust_bridge is currently broken for web development. I have a PR open, but it's running into weird issues with the CI and so can't be merged.

For reference, https://github.com/fzyzcjy/flutter_rust_bridge. And dart is a really nice language too, my only real gripe is that I'm no longer used to [type] [variable] over [variable]: [type]

https://github.com/fzyzcjy/flutter_rust_bridge (Fixed your href)

It appears that this is indeed what was happening. The issue has now been fixed in the template.