druid VS kas

If you want a "native-like" toolkit like Qt but Rust-native, then Druid, KAS and Iced are the most advanced in my opinion (though all are incomplete).

Druid (https://github.com/xi-editor/druid) is really cool actually for making nice looking GUIs with low memory footprint and minimal executable size, it's still experimental, but worth to try. Also take a look as Iced, Concord

Qt classic/widgets? I'm developing Kas to offer vaguely similar features (e.g. data models, theme abstraction, custom widgets with complex event handling), though said event handling and data models are quite different. It's still got a long way to go (so API is not stable), but in case you are interested, I should be dropping a new release tomorrow.

KAS GUI

kas-wgpu looks hopeful, but there's very little information about it and I'm not even sure it works on Android.

Changelog

The next release will support dynamic linking which approx. halves the recompile time in my quick tests. This is based on Bevy which also recommends using LLD (see here); I didn't have much success with this yet however.

If you want a "native-like" toolkit like Qt but Rust-native, then Druid, KAS and Iced are the most advanced in my opinion (though all are incomplete).

Yes. It was actually a mistake (using a nightly compiler and not realising the lock-in). But in this case (with KAS still in "earlyish development" and the workaround being less concise), I decided to leave it.

This is a little library I've been using recently (original version here).

Hello, I am github.com/dhardy, maintainer of rand, former dev of OpenMalaria epidemiology simulator, author of KAS GUI and Rust enthusiast since 2013. I may be interested in positions within Europe.