webrtc VS tauri

There is a WebRTC protocol implementation in Rust; it is webrtc-rs. This repository provides some examples that include SFU, but we still need to write a lot of code to implement a practical SFU server. In addition, existing repositories implementing SFU servers with webrtc-rs weren't directly usable for my needs.

This is not true, there are actually multiple WebRTC implementations in different languages besides the reference library: aiortc (python), libdatachannel (C++), sipsorcery (C#),webrtc-rs (rust), werift (Typescript), and Amazon Kinesis (C)

I am trying to get WebRTC working using Rust https://github.com/webrtc-rs/webrtc

I have opened an issue on GitHub [1], we can continue there.

[1] https://github.com/webrtc-rs/webrtc/issues/426

webrtc

Early in the development journey, the decision came to use either Tauri or Electron to build the app. Using one of these frameworks offered a promising way to avoid writing native code for each platform (Windows, macOS, Linux). This meant a crucial choice needed consideration.

Tauri is a desktop application framework that serves as an alternative to Electron. (From Tauri v2, it also supports mobile apps.)

Tauri is a Rust-based library that enables you to build lightweight desktop applications by leveraging web technologies like HTML, CSS, and JavaScript for the UI. You can use any frontend framework of your choice that compiles to HTML, CSS, and JavaScript. Unlike Electron (a JavaScript desktop app development framework), which relies on Chromium and Node.js, Tauri uses the system's native web view.

Then I learned Tauri and used my favourite frontend framework SolidJS with TailwindCSS and DaisyUI to build the UI with MotionOne to add animations and Tauri to build the desktop/web/android/ios app.

tauri dev is incredibly slow

Are the memory benchmarks measured correctly?

This tauri issue suggests the common measurement approach might be wrong

https://github.com/tauri-apps/tauri/issues/5889

Also would be better to have specific startup time instead of "fast" (which is strange since electron is not known for fast startup)

Here is a whole story: https://github.com/tauri-apps/tauri/discussions/4089

tl;dr - Tauri uses platform's default implementation of a webview. On Windows it's WebView2 which reports back to MS.

I mean, most OSes already ship with a WebView component that you can use instead of shipping an entire browser runtime.

Wails does that: https://wails.io/

Tauri also does that: https://tauri.app/

That does help with the needed resources quite a bit: https://github.com/Elanis/web-to-desktop-framework-compariso...

Sadly it doesn’t change the memory usage much so the technology is still inherently wasteful, but on a certain level it feels like a lost battle - because web technologies often feel like the choice of least resistance when you want GUI software that will run on a bunch of platforms while not being annoying to develop (from the perspective of your run of the mill dev).

HTML/CSS can still be used for the frontend even without Electron. Some frameworks use the OS bundled web renderer instead:

- For Rust apps: https://github.com/tauri-apps/tauri

- For Go apps: https://github.com/wailsapp/wails