DAdagmx·Jun 17, 2024
UI libraries are a poor reason to pick Rust over Swift, given that Rust has a very poor UI story.
Doesn’t your comment apply very equally to Rust? There’s basically Slint and Tauri, and several bindings in various states of disarray. Not exactly very compelling.
The Rust ecosystem has very many strengths, but UI is not one of them.
Regardless, you’re incorrect about there being no way to make GUI applications
Here’s a Gnome binding https://swift.org/blog/adwaita-swift/
The C++ interop allows easy binding to Qt https://github.com/qt/qtdeclarative/tree/dev/tests/manual/he...
Win32 https://github.com/compnerd/swift-win32
The fact that Swift has easier C++ interop than Rust makes the cross platform UI story much easier and more compelling than what I’ve found in Rust.
Bindings are much simpler to manage and can be handled by a single module m
Read the rest
ap file with a single line in it most of the time.
Adding to that, many well established UI libraries depend on classes to implement them. Rusts lack of classes, while wonderful otherwise, makes binding to heavy class based libraries very onerous.
Don’t get me wrong, I really enjoy rust. It’s just, it’s very ill suited for UI work today itself. I almost always write my UI side in C++ if I have to and bind over when needed instead.