This whole thread reads like it is really bad idea to use webtech for desktop applications.
Show HN: I rewrote my Mac Electron app in Rust
221–230 of 465 posts
Re: Show HN: I rewrote my Mac Electron app in Rust
#222Earlier quoted context omitted.
We actually haven't rolled out cross platform support yet with the Tauri version, so we will see how that goes. Our UI needs are simple, luckily. What kind of rendering differences were you seeing with Tauri? Was there one platform that worked the best/worst for your app? We'd love to support Windows next. With the Electron version of the app, we had issues running our bundled binaries on Macs with Intel chip. That c…
Tauri 2.0 migration can potentially give you some more performance benefits, because they've greatly enhanced the JS-Rust bridge especially when you're moving lots of data.
Re: Show HN: I rewrote my Mac Electron app in Rust
#223Earlier quoted context omitted.
We actually haven't rolled out cross platform support yet with the Tauri version, so we will see how that goes. Our UI needs are simple, luckily. What kind of rendering differences were you seeing with Tauri? Was there one platform that worked the best/worst for your app? We'd love to support Windows next. With the Electron version of the app, we had issues running our bundled binaries on Macs with Intel chip. That c…
> I recently went the other way (started a project in Tauri, moved to Electron) because of frustration with rendering differences between the web views employed on different platforms. This is our #1 frustration with Tauri. The OS-provided system webviews are not stable, repeatable, consistent platforms to build upon. Tauri decided that a key selling point of their platform was that Tauri builds won't bundle a browse…
So use Electron and FFI, it's not that hard
Re: Show HN: I rewrote my Mac Electron app in Rust
#224I'm dragging my feet about porting my Python Qt app to Rust, because I feel that no Rust GUI library is as rich as Qt and I know that I'll get stuck with that at some point.
Re: Show HN: I rewrote my Mac Electron app in Rust
#225The UI appears simple enough to be implemented in any desktop GUI library. Why did you decide on using web technologies? Is it because of the libraries you are using in the app?
Re: Show HN: I rewrote my Mac Electron app in Rust
#226Earlier quoted context omitted.
But the thing is, if you're using Tauri, you control the web app. So you need to test it on WebkitGTK, I guess that's the extra burden?
Have you actually tried deploying to webkitgtk ever? Good luck "testing" your video conferencing app on webkitgtk - it doesn't support webrtc! It is still useful to test your error page I suppose. Note that this is one example among many of missing features, bugs and/or horrible performance. Here's a preview: no notifications, no :has, no TLA. (Not blaming the epiphany devs for the situation here to be clear)
Re: Show HN: I rewrote my Mac Electron app in Rust
#227This whole thread reads like it is really bad idea to use webtech for desktop applications.
Re: Show HN: I rewrote my Mac Electron app in Rust
#228I recently went the other way (started a project in Tauri, moved to Electron) because of frustration with rendering differences between the web views employed on different platforms. Have you run into any cross platform UI bugs since you switched? It looks like your UI needs are pretty simple while computation is complex so the extra QA tradeoff would still be worth it for you. I'm just wondering if my experience was…
I guess the Web would be all much better if ChromeOS Platform was everything that remained, who needs standards and multiple vendors.
Re: Show HN: I rewrote my Mac Electron app in Rust
#229Looks awesome. I work closely with Multimodal search and have had trouble porting CLIP to ONNX and other formats due to the lack of multi-head attention operators. Are you using Python for the CLIP inference, or did you manage to port it to a format hostable in a Rust or C/C++ inference runtime?
Re: Show HN: I rewrote my Mac Electron app in Rust
#230Earlier quoted context omitted.
Tauri 2.0 migration can potentially give you some more performance benefits, because they've greatly enhanced the JS-Rust bridge especially when you're moving lots of data.
We picked egui instead of tauri because we had more rust skills than web skills. Other than rastered text, whoch I can't find any customers who actually care, are there good reasons to go tauri? It seems widely used, but also widely complained about.
Would you have any webpage or product info, possibly with screenshots?
We're building an in-house DCC with egui so I'm curious.