Ask HN: If Dart can do it, then why can't Rust?
I am reading through Dart and Flutter tutorials. And I was wondering, if Dart can be used for developing multiplatform UI, then why can't Rust be used to develop multiplatform UI? What are the challenges?
10 comments
[ 5.5 ms ] story [ 34.9 ms ] threadI'm looking into a multiplatform app myself, and I've considered egui and iced, but am leaning towards Tauri. I'll definitely be sticking with Rust (this is a front end for a Rust library that I currently use from a cli). But still interested to hear more on Flutter's advantages in general.
There are many other nice Rust GUI libraries depending on your needs:
https://www.areweguiyet.com/
Dart/Flutter is clearly further along. The main non-technical reason for this is that Flutter is the single blessed UI toolkit for Dart, whereas Rust instead relies on the creative chaos of multiple competing and/or overlapping open source projects. The Dart approach concentrates effort and removes the burdens of choice and intergration from app developers; the Rust approach has more potential for arriving at novel solutions, and is less likely to get trapped by top-down decisions.
It's all pretty promising, and great to have some alternatives to the rather creaky old toolkits we have. I personally think web tech will continue to be a strong contender or many multiplatform apps (for which - Rust has Tauri).
We (my last team) have been developing cross platform, production ready, multiplatform tools, WITH UI for at least 2 years now; And that was 3 months after starting to use Rust.
Please could you share details on what UI library/framework you are using? And what all platforms your UI is targeting?
The difference between Dart and Rust is that Dart is developed solely (or mostly) by Google and therefore Flutter is the one true way to do UI.
With Rust, you have many options none of which are the obvious choice.