3 ms·
> And if your user has the correct runtime for the webview used by Tauri you can just send them a single executable So does this mean all these comparisons are
by pkulak 4y ago
> And if your user has the correct runtime for the webview used by Tauri you can just send them a single executable
So does this mean all these comparisons are between a web bundle that runs on an existing VM, and a web bundledthat came packaged with a VM? Because I thought the whole point of Electron was that all the dependencies came packaged together, even if that adds 100 megs to the install.
- esprehn 4y agoYup. Tauri is more like Ionic or Cordova than Electron. You get a mostly web based developer experience, but without the browser matrix simplification so you're still at the whim of the system WebView capabilities for the view layer. The good news is the built in webviews have come a long way since webcompat is much better across browsers, but it's still extra things to worry about and can produce problems on old MacOS or Windows pre-11. See also: https://tauri.app/v1/guides/architecture/process-model https://tauri.app/v1/guides/architecture/process-model https://tauri.app/v1/api/js/ https://tauri.app/v1/api/js/
- chippers 4y agodisclaimer: contributor to Tauri This ends up often being my main contention with Rust, when making useful programs it often leads to large compile times mostly due to the linker. The mold linker can help greatly, but it's still not a great developer experience. Something I want to create in the future is a fully compiled Tauri application except it takes the webview sources at runtime, allowing a fast-as-possible development reload as long as you are only touching the frontend application and not the Rust side. On the Rust side there are a few options, one of them being developing something like WASM plugins on the backend where their individual dependencies are much less than a full application.