would be great to have Rust bindings so it could work with Tauri. With tauri growth and the upcoming mobile devices support coupled with SQLite recent hype, this could bridge the gap and solve many problems for offline-first apps, thus become the go to solutions for many dev shops.
I'm looking to add Rust bindings to ElectricSQL as that is a similar sync solution but it acts on the database layer so it's language agnostic. I'm using Rust on the server but Rust bindings would work on both the client and server. If you're interested in joining me on developing those Rust bindings, let me know.
Yes but the 'backend' (the client, but the non-presentational bit) is Rust; it'd be there you'd want to do this sort of synchronisation or anything to do with state/database. You could absolutely shoe-horn it in, it just wouldn't be the way you'd expect it to work or feel particularly right/supported.
Comments
would be great to have Rust bindings so it could work with Tauri. With tauri growth and the upcoming mobile devices support coupled with SQLite recent hype, this could bridge the gap and solve many problems for offline-first apps, thus become the go to solutions for many dev shops.
I'm looking to add Rust bindings to ElectricSQL as that is a similar sync solution but it acts on the database layer so it's language agnostic. I'm using Rust on the server but Rust bindings would work on both the client and server. If you're interested in joining me on developing those Rust bindings, let me know.
I thought Tauri was just using native web renderers? Seemingly Triplit should work out of the box.
Yes but the 'backend' (the client, but the non-presentational bit) is Rust; it'd be there you'd want to do this sort of synchronisation or anything to do with state/database. You could absolutely shoe-horn it in, it just wouldn't be the way you'd expect it to work or feel particularly right/supported.
Got it, that makes sense. Probably could spin up Node process but of course that requires having Node installed or bundled with the app.