vizia VS flutter_rust_bridge

All of these projects have in common that they use Taffy (the project that I work on!) for box-level layout (which currently gives them block, flexbox, and grid layout) , and are either using or planning to use cosmic-text for text/inline layout. This gives you a decent first approximation of web layout, but it's not perfect and there are major features like float, display: inline-block, position: static, box-sizing: content-box missing. Not to mention that none of these implementations currently resolve CSS selectors, so you are effectively limited to inline styles (if you're interested in something in that direction then you may be interested in https://github.com/vizia/vizia).

Vizia is basically fine-grained reactivity with an Elmish twist, though I haven't used it, so I couldn't say how well it works.

There are a number of up-and-coming Rust-based frameworks in this niche:

- https://github.com/iced-rs/iced (probably the most usable today)

- https://github.com/vizia/vizia

- https://github.com/marc2332/freya

- https://github.com/linebender/xilem (currently very incomplete but exciting because it's from a team with a strong track record)

What is also exciting to me is that the Rust GUI ecosystem is in many cases building itself up with modular libraries. So while we have umpteen competing frameworks they are to a large degree all building and collaborating on the same foundations. For example, we have:

- https://github.com/rust-windowing/winit (cross-platform window creation)

- https://github.com/gfx-rs/wgpu (abstraction on top of vulkan/metal/dx12)

- https://github.com/linebender/vello (a canvas like imperative drawing API on top of wgpu)

- https://github.com/DioxusLabs/taffy (UI layout algorithms)

- https://github.com/pop-os/cosmic-text (text rendering and editing)

- https://github.com/AccessKit/accesskit (cross-platform accessibility APIs)

In many cases there a see https://blessed.rs/crates#section-graphics-subsection-gui for a more complete list of frameworks and foundational libraries)

I don't think it's actually merged into Iced yet. It is merged into https://github.com/vizia/vizia though.

Vizia

I have recently learned about https://github.com/vizia/vizia and it looks very promising to me

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.