While I like Tauri being light weight, its rust backend and support for mobile, I'm considering moving to electron now.

The webviews on different platforms are very fragmented. they support different feature sets and have different bugs. For example, on mac, I have seen svg and pdf rendering bugs I don't know when they will be fixed. I can't predict their behaviors on platforms I have no access to.

Tauri is also too young, I have seen its new window system crashes on users' machines. And as for the sidecar/external binary feature, Tauri doesn't fix the rpath when packaging, you will have to solve it using manual solutions.

I love rust, but many solutions are only available in c++. rust bindings are usually maintained by hobbyists and rarely updated. I have no energy to fix the binding issues.

I'm now going back to electron, so my frontend can use webgpu. As for the backend, I'm planning to write nodejs addons in c++ and rust.

Fair points all of them.

With the side car support we haven't faced any issues so far tbh (on windows and macOS).

Also I agree that the lack of wgpu is annoying. This is why for our cursor rendering (our sidecar) we are just using winit with wgpu. We are thinking of trying egui for our cursor rendering and then maybe try to integrate it with Tauri and remove the sidecar completely.

Our frontend is quite simple so we don't need wgpu there. Though I agree 100% that with electron you will have less surprises.

Hopefully our experiment won't come back to bite us and we will be able to contribute back to the community.

We have done this move at Caido despite being a rust shop for the reason you mentionned. The webviews on OS are garbage in 25-35% of the time and will cause 90%+ of your bug report.

Switched to electron and moved on. Almost nobody cares about the memory footprint and the binary size. But they will care then app is half broken on their 9 years out of date webview...