| For me, the best about Tauri is that: - We can embed an existing application using a sidecar [1]. - Now, we can also use Elixir in the backend, embed the BEAM, and deliver a single binary, see ElixirKit [2]. As far as I know, LiveBook Desktop [3] is using Tauri for building binaries for MacOS and Windows. If Tauri works for the Elixir team, I think it works for me too. Also, I know that Tauri is not bullet proof. WebView can be limited for some use cases, see [4]. There is some effort to use CEF to mitigate those problems, though [5]. I'd like to know how Deno Desktop compares with Tauri in this context. I know it is a new product, not sure if we could bundle an existing binary in Deno Desktop, like in ElixirKit. [1] https://v2.tauri.app/develop/sidecar/ [2] https://elixirkit.hexdocs.pm/tauri.html [3] https://github.com/livebook-dev/livebook/blob/main/rel/app/t... [4] https://www.youtube.com/watch?v=vmslGvxObvM&t=621s [5] https://github.com/orgs/tauri-apps/discussions/8524 |
And you can embed anything on the binary with `deno desktop --include […]`.