For electron based apps, most part of the codebase runs on the chrominum front-end - written in JavaScript / HTML. Usually only some critical code runs on the node backend.
As such then, the proposal from tauri is to run majority of the application in JavaScript / HTML ecosystem, while the critical parts can be offloaded to Rust. Even the filesystem access is possible in JavaScript side itself.
> the proposal from tauri is to run majority of the application in JavaScript / HTML ecosystem
That's a decision the developer has to take, but I'd rather see it as the opposite: the sensible approach is to run just the UI related things in Javascript, and run almost all of your business logic in Rust.
That's how I use it too, mostly because I personally find JavaScript and typescript frameworks harder to use than rust. Managing data in js is hard for me without static typing. Everyone will have different comfort levels but I agree, business logic in rust, front end in js is a great separation.
Well I agree that it is already a good tradeoff, being able to offload the most intensive tasks to Rust, which is really performant. However my perspective is that of a C++ developer already, so I like Rust as a "better C++"... it's just that I'm not sure others will see it with such kind eyes :-)
On a tangent, I've been forced to learn and use Swift the last couple weeks, and to my surprise it has been a delight! If it had a more cross-platform spirit, I think I might have found a new favorite of mine for general application development.
As such then, the proposal from tauri is to run majority of the application in JavaScript / HTML ecosystem, while the critical parts can be offloaded to Rust. Even the filesystem access is possible in JavaScript side itself.
From that sense I feel this is a good tradeoff.